Bug#808546: RFS: node-restore/0.3.0-1 [ITP] -- simple RemoteStorage server written in Node.js

Control: owner -1 ! Control: tags -1 moreinfo Hi, lets review: http://debomatic-amd64.debian.net/distribution#unstable/node-restore/0.3.0-1/lintian lintian needs fixing I: node-restore source: xs-testsuite-header-in-debian-control xs-testsuite I: node-restore source:

Bug#810853: RFS: moosefs/2.0.83-1 [ITP] -- fault tolerant, reliable, highly available, highly performing, scaling-out network distributed file system

>Il Martedì 12 Gennaio 2016 22:52, Piotr Robert Konopelko > ha scritto: >I forgot to mention, that MooseFS fork - LizardFS is a fork >of *old* MooseFS version - 1.6.27-5 which is a far behind >2.0.x (stable) or 3.0.x (curent / testing). > >(Far behind = since MFS

Bug#810853: RFS: moosefs/2.0.83-1 [ITP] -- fault tolerant, reliable, highly available, highly performing, scaling-out network distributed file system

(wrong hotkey) Hi, If you think it is a full and better replacement of LizardFS, you need to talk with LizardFS maintainer, reachable at https://packages.qa.debian.org/l/lizardfs.html cheers, Gianfranco

Re: RFS: snetmanmon, a simple network manager and monitor

Hi, >The copyright for snetmanmon isn't autogenerated, it's part of the >README. What I'm generating here is the file which is necessary for the >debian package, mainly because I don't want to have the GPL in the >standard LICENSE file and in debian/copyright. And that is something I >likely

Bug#807700: RFS: steamcmd - Command-line interface for Steam

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: owner -1 ! Control: tags -1 moreinfo Hi, packaging stuff/binaries randomly donwloaded from the internet is somewhat a no-go for Debian in general. some additional remarks: you are exposing an i386 package, but I think it runs on amd64

Re: RFS: snetmanmon, a simple network manager and monitor

Hi, such requests disappears quickly from the mentors list. Can you please open an RFS bug for your package? https://mentors.debian.net/sponsors/rfs-howto >I'm unsure if I have to provide an already built package too. you don't need, it is stripped by mentors.d.o website, and useless in a

Bug#747032: RFS: libjs-zxcvbn/1.0+dfsg.2-2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Ben > The latest source package is now online at > . > Hi Ben do you still need a sponsor? there is a new upstream release, let me know if you want another review+upload :) cheers, G.

Re: help2man usage with pybuild / debhelper packaging workflow

Hi, sending what I do on my machine >Il Venerdì 3 Giugno 2016 17:44, Ghislain Vaillant ha >scritto: >Dear all, > >Are there any successful examples of integration of help2man with a >pybuild / debhelper workflow for an arbitrary number of scripts? > >The only close example

Bug#826266: RFS: dvtm/0.15-1~bpo8+1 ITP

control: owner -1 ! control: tags -1 moreinfo Hi, >http://mentors.debian.net/debian/pool/main/d/dvtm/dvtm_0.15-1~bpo8+1.dsc 404 G.

Bug#811426: RFS: golang-github-kennygrant-sanitize/1.0-1 [ITP]

control: tags -1 moreinfo On Sun, 15 May 2016 15:59:09 + Mattia Rizzolo wrote: > On Mon, Jan 18, 2016 at 12:09:14PM -0800, Nathan Osman wrote: > > I am looking for a sponsor for my package > > "golang-github-kennygrant-sanitize" > > >

Bug#816683: RFS: cloudabi-utils/0.8-1 [ITP]

control: tags -1 moreinfo Setting moreinfo until the blocking bug is resolved. G. signature.asc Description: OpenPGP digital signature

Bug#826135: RFS: lsvpd/1.7.6-1 ITP: lsvpd -- Utility to List Device Vital Product Data (VPD)

Hi >Spaces are not allowed in license names. But here the license name is >just “GPL-2+”. > >Let me quote the relevant part of the spec: >“An exception or clarification to a license is signalled in plain text, >by appending ‘with exception’ to the short name.” probably when I tried a) this

Bug#814680: RFS: stp/2.1.2+dfsg-1 [ITP] -- Simple theorem prover

control: tags -1 moreinfo Hi, On Wed, 9 Mar 2016 20:48:46 -0800 Afif Elghraoui wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, Marko, > > On الأحد 6 آذار 2016 14:53, Marko Dimjašević wrote: > > > > On Fri, 2016-02-26 at 17:42 -0800, Afif

Bug#816652: RFS: compiz/1:0.9.12.2 [ITP:722451]

control: tags -1 moreinfo Setting moreinfo tags, until the first review is fixed. Gianfranco signature.asc Description: OpenPGP digital signature

Bug#826661: RFS: groonga/6.0.4-1

control: owner -1 ! control: tags -1 moreinfo Hi >I am looking for a sponsor for my package "groonga" Hi, I did a debdiff between them, and I see some changes that might be ABI breaking the library: -GRN_API grn_rc grn_timeval_now(grn_ctx *ctx, grn_timeval *tv); -GRN_API grn_rc

Re: ITA for an abandoned package: evolver case

Hi, >i am maintaining many packages, which were maintained by Adam >originally. But all of them are team-maintained (Debian Science), and this >one is not. > >AFAIK Adam is not active in Debian last several years. From my point of >view, it will not be too offensive, if evolver will be moved

Re: ITA for an abandoned package: evolver case

Hi, >May I fill an ITA or something to signify that someone to working >the [surface] evolver package ? A bug with patches should be enough, ITA means somebody orphaning the package and only the maintainer/MIA team can do it. But a bug with patches and you proposing the maintainership is

Re: ITA for an abandoned package: evolver case

Hi, >Right now the package rocks. >But the upstream version is (very) old, and the Debian package material >clearly needs some refreshment. Is a patch really appropriate here ? >May I rather wait for clear orphaning instead ? I see (2.30 VS 2.70)... what about: gbp import-dscs --debsnap

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

Hi On 06/06/2016 03:53, Carlos Donizete Froes wrote: > Hello Gianfranco, > > I made the changes recommended me. Please could again analyze my > package? > > https://mentors.debian.net/package/runescape > > Thank you! > Hi some more issues: 1) you put dependencies under build-dependencies,

Re: Help with CMake linking Debian's LLVM libs

Hi, >$ ./debian/rules build which llvm version did upstream bundle? LLVM folks are known for breaking API between releases, so maybe just you need a specific llvm version rather than the default one. G.

Bug#826135: RFS: lsvpd/1.7.6-1 ITP: lsvpd -- Utility to List Device Vital Product Data (VPD)

control: tags -1 moreinfo >https://mentors.debian.net/package/lsvpd can you please remove moreinfo once the package enters unstable? thanks G. > the same for libvpd applies here > > "License: GPL-2+ with librtas exception" > > maybe something like > License: GPL-2+-with-librtas-exception

Bug#826138: RFS: servicelog/1.1.14-1 ITP: servicelog -- Platform Service/Error Message Database

On Thu, 2 Jun 2016 16:27:59 +0000 (UTC), Gianfranco Costamagna <locutusofb...@debian.org> wrote: > control: owner -1 ! > control: tags -1 moreinfo > > Hi, in additions to the other stuff: > > > GPL-2+ seems the right license. > > other stuff LGTM >

Bug#826137: RFS: libservicelog/1.1.16-1 ITP: libservicelog -- Library to create and maintain a database for storing events

usr/lib/powerpc64le-linux-gnu/libservicelog.so -> libservicelog-1.1.so.1.0.0 F. On Thu, 2 Jun 2016 16:23:45 + (UTC), Gianfranco Costamagna <locutusofb...@debian.org> wrote: > control: owner -1 ! > control: tags -1 moreinfo > > Hi, > the same for the other two librarie

Bug#826140: RFS: ppc64-diag/2.7.0-1 ITP: ppc64-diag -- Platform error log analysis tool and rtas_errd daemon

thout-manpage usr/sbin/ppc64_diag_register W: ppc64-diag: binary-without-manpage usr/sbin/rtas_errd Those are scripts called by systemd unit files. Is it acceptable or should they be moved to another place? I saw both cases in codesearch.d.n Thanks, F. On Thu, 2 Jun 2016 16:32:05 +0000 (UTC), Gianfranco C

Bug#826661: RFS: groonga/6.0.4-1

hi >* experimental APIs >* stable APIs fair enough. sponsored. G.

Bug#826160: RFS: node-getobject/0.1.0-2 -- set and get deep objects easily

Hi, > I am looking for a sponsor for my package "node-getobject" sponsored. G. * Package name: node-getobject Version : 0.1.0-2 Upstream Author : "Cowboy" Ben Alman * URL : https://github.com/cowboy/node-getobject * License

Bug#821270: Review of git version

Hi, after the latest fixes I put the package in deferred/5, to leave Sean enough time to review it and ack the latest changes. thanks for the nice contribution to Debian! G. Il Mercoledì 1 Giugno 2016 12:51, nord-stream ha scritto: Source:

Bug#827043: RFS: gdbm/1.12-1 ITP

control: owner -1 ! control: tags -1 moreinfo Hi, >Il Sabato 11 Giugno 2016 18:21, Sven Joachim ha scritto: yes, please fix what Sven pointed out (with a great thanks from me) I can just add some little additional notes (please note: I didn't do a full review, without the

Bug#827043: RFS: gdbm/1.12-1 ITP

Hi, >My bad. I should put 'apt-get update' into cron. or use "pull-debian-source packagename [version]" :) >Sent it. Seems I can't include control into message to >826...@bugs.debian.org package is now in QA >I considered some of them. Other require more prolonged >experimentation on my

Bug#827085: RFS: growl-for-linux/0.8.4-1 [ITP]

control: owner -1 ! control: tags -1 moreinfo Hi, >I am looking for a sponsor for my package "growl-for-linux" lets review: 1) I really don't like a 2k lines long changelog for an initial inclusion. most of the lines are "backport to dist foo" I would just delete them, keeping a public

Re: Restore Iceweasel branding

Hi, >Can we do something to make this available to the users as soon as >possible? Now firefox-esr is out for stable users, too. the current package needs to migrate in testing first, and then you need to check with -release team if a stable-proposed-update is feasible or not (I see esr is in

Bug#827149: RFS: triggerhappy/0.4.0-1

control: owner -1 andrew.shado...@gmail.com >I think I could. setting you as owner :) >There's https://github.com/wertarbyte/triggerhappy/commits/systemd but >I haven't looked how much does it conflict with the master branch. I did merge the systemd branch into master, and it merged

Bug#827090: RFS: runit/2.1.2-4 ITP

control: owner -1 ! control: tags -1 moreinfo >I am looking for a sponsor for my package "runit" lets see 1) + * New maintainer did Gerrit asked for help? stepping in as maintainer needs an RFH or Orphan package. (well, Gerrit was fine on giving up some packages IIRC) 2) compat level 10 not

Bug#820644: RFS: libretro-snes9x [ITP]

Hi, fixed the summary (please keep the RFS in cc, otherwise I can easily forget because the package in this topic is already sponsored) >CPPFLAGS is actually for both c and cpp: yep I know >I can avoid "hardening-no-fortify-functions" only if there's a> CPPFLAGS in >the cpp line. sure

Bug#827085: RFS: growl-for-linux/0.8.4-1 [ITP]

Hi, >I deleted them and added notes about original maintainer for simplicity. wonderful >Applied above, then enabled pie explicitly for gol again to make package in >good shape. I see, nice! >I'll apply patch when actually it is needed. let me disagree a little bit :) people might

Bug#827149: RFS: triggerhappy/0.4.0-1

control: owner -1 ! >Hi, could you please also ship my systemd integration (see upstream PR and >branch)? Andrew, do you plan to upload the package once this is fixed? I see Jakub already did a wonderful review, and the current package on mentors seems to address his concerns. I see your

Bug#827043: RFS: gdbm/1.12-1 ITP

Hi Jakub and Dmitry (ccing you both, not sure if you are subscribed to the bug) >You are probably[0] referring to: > >P: gdbm source: license-problem-gfdl-non-official-text doc/gdbm.info invariant >part is: with no invariant sections, no front-cover, and no back-cover texts >P: gdbm source:

Re: how to build packages with a specific complier ?

Hi, >It appears that some tests fail for one of my package (gmp-ecm) on one >architecture (s390x): >after some investigation, it appears that it is a compiler issue: building >with gcc-6 (instead of gcc-5) >causes no issue. So now I want to impose the gcc-6 to d/rules ? What is the >best way

Re: Restore Iceweasel branding

Hi, >Why do you think it would be useless? the "bug" is introduce with a stable-release-update, and should be fixed with another s-p-u fixing it with a backport means the user should be aware of the fix in another pocket, enable it, install it, and so on. I guess having both "issue" and "fix"

Bug#827089: RFS: dh-runit/0.1 ITP

control: owner -1 ! control: tags -1 moreinfo >I am looking for a sponsor for my package "dh-runit" while I did some work on runit package a while ago, I'm not sure about how you want the packages to use your new shiny dh call? how do you plan to notify them about it? do you plan to open a lot

Re: Adding runtime dependencies that aren't caught by shlibs:Depends

Hi Jens! >- first find the library file on the system (looking in some > hardcoded directories), I'm really sure it won't add any value to your current solution, but you might consider asking ld or whatever the list of search paths

Re: Help for backport of seer wanted (may be libhdf5 problem?)

Hi, a quick search on codesearch.d.n [1] shows that armadillo might be your answer :) [1] https://codesearch.debian.net/results/arma_H5T_NATIVE_DOUBLE/page_0 G. Il Lunedì 30 Maggio 2016 11:10, Andreas Tille ha scritto: Hi, I intend to backport seer[1] but I was running

Re: Help for backport of seer wanted (may be libhdf5 problem?)

Hi Andreas, >installed while a build in a Jessie+backports chroot fails. Do you think the >solution is that simple as backporting armadillo 6.700.6+dfsg-1 ? pbuilder-dist jessie login, enable backports apt-get build-dep seer dpkg-buildpackage (fails) enable stretch repo apt-get update &&

Bug#825904: RFS: python-model-mommy/1.2.6-1

control: owner -1 ! control: tag -1 moreinfo Hi, looking at requirements.txt, seems that six is used grep six . -R |grep import ./model_mommy/utils.py:from six import string_types ./model_mommy/generators.py:import six ./model_mommy/recipe.py:from six import string_types

Bug#825531: RFS: libcork/0.15.0+ds-1 [ITP]

control: owner -1 ! control: tags -1 moreinfo Hi, I did a quick look and the package looks great! (I grabbed it from mentors) however I have some things I would like to discuss / see fixed: 1) W: libcork source: debian-watch-file-should-mangle-version line 7 2) lrwxrwxrwx root/root

Bug#825532: RFS: shadowsocks-libev/2.4.6+20160526+ds-1 [ITP]

control: tags -1 moreinfo control: owner -1 ! hi, 1) I: shadowsocks-libev: extended-description-is-probably-too-short 2)W: shadowsocks-libev source: debian-watch-file-should-mangle-version line 7 3) Replaces: shadowsocks (<< 1.5.3-2) Breaks: shadowsocks (<< 1.5.3-2) Why? 4)libipset/ <--

Re: header dependencies

Hi, >Say a package installs only headers, and in one of those, a header of another >-dev package is #included. How to depend on the package? I would call it libfoo-dev (arch:all) and depend (runtime) on libbar-dev. Feel free to steal from websocketpp, a source-only library I maintain.

Re: Trying to disable error=format-security for clapack

Hi, > E: libclapack3: binary-or-shlib-defines-rpath > usr/lib/x86_64-linux-gnu/libclapack.so.3.2.1 > /build/clapack-3.2.1+dfsg/obj-x86_64-linux-gnu/BLAS/SRC >Is there any trick how I could tweak cmake files to prevent the >inclusion of rpath or is the only chance to solve this to use > >

Re: Finding sponsor

yes, Debian Haskell Group (in cc) might give you some hints :) G. Il Giovedì 2 Giugno 2016 14:47, Marwan Rabbâa ha scritto: but still have a question this app is in haskell and I built i with stack https://www.stackage.org I do not thing stack use internal

Bug#809623: telegram-purple package has been removed from Mentors

Hi, feel free to reopen whenever you want :) G. Il Giovedì 2 Giugno 2016 12:36, Ben Wiederhake ha scritto: Control: close -1 Control: thanks Am 02.06.2016 um 05:25 schrieb mentors.debian.net: > Your package telegram-purple all versions has been removed from >

Bug#826138: RFS: servicelog/1.1.14-1 ITP: servicelog -- Platform Service/Error Message Database

control: owner -1 ! control: tags -1 moreinfo Hi, in additions to the other stuff: GPL-2+ seems the right license. other stuff LGTM (please also run check-all-the-things/lintian and fix stuff) cheers, G. Il Giovedì 2 Giugno 2016 18:09, Frederic Bonnard ha

Bug#826140: RFS: ppc64-diag/2.7.0-1 ITP: ppc64-diag -- Platform error log analysis tool and rtas_errd daemon

control: owner -1 ! control: tags -1 moreinfo Hi, in additions to the other reviews, lintian and check-all-the-things, please: why no-doc package? I see doxygen here other stuff LGTM Il Giovedì 2 Giugno 2016 18:12, Frederic Bonnard ha scritto: Package:

Bug#826141: RFS: skiboot/5.2.2-1 ITP: skiboot -- OPAL boot and runtime firmware for POWER

control: owner -1 ! control: tags -1 moreinfo Hi, also here, please check the usual stuff (also cppcheck is reporting some issues) General note: I suggest you to do only one of the reviews, and fix all of them. I prefer to see only one package at each time, sponsor it, wait for you to fix the

Bug#820644: RFS: libretro-snes9x [ITP]

control: owner -1 ! control: tags -1 moreinfo can you please fix the lintian stuff? http://debomatic-amd64.debian.net/distribution#unstable/libretro-snes9x/1.53+git20151206-1/lintian specially the copyright stuff. G. On Sun, 22 May 2016 17:50:52 -0300 =?UTF-8?Q?S=c3=a9rgio_Benjamim?=

Bug#820751: RFS: emulationstation/2.0.1a [ITP]

Hi, please fix lintian http://debomatic-amd64.debian.net/distribution#unstable/emulationstation-theme-simple/1.4-1/lintian look at the comments on mentors page https://mentors.debian.net/package/emulationstation and lintian for the main package.

Bug#826134: RFS: libvpd/2.2.5-1 ITP: libvpd -- VPD Database access library

control: owner -1 ! control: tags -1 moreinfo Hi, lets see: usr/include/libvpd-2/* usr/lib/*/*.so usr/lib/*/pkgconfig/* maybe you can put usr/include usr/lib/*/*.so usr/lib/*/pkgconfig (I didn't check the above) and for the library you can do something like usr/lib/*/lib*.so.*

Bug#826135: RFS: lsvpd/1.7.6-1 ITP: lsvpd -- Utility to List Device Vital Product Data (VPD)

Hi, >The same... what? I can't parse this sentence. the same review done for the other packages applies to this one (yes, indeed I should have written it better, I explained it somewhere else) >"FOO with BAR exception" is a valid licence syntax in DEP-5.>If it is not >appropriate to use it

Bug#820704: Bug#820705: RFS: subuser/0.5.6-3 [ITP]

control: owner -1 ! control: tags -1 moreinfo Hi, lets see: "export PYTHON=`which python3`" what? http://debomatic-amd64.debian.net/distribution#unstable/subuser/0.5.6-1/lintian please fix the first lintian warning. "Depends: ${misc:Depends}, ${python3:Depends}, python3-setuptools, git,

Bug#826135: RFS: lsvpd/1.7.6-1 ITP: lsvpd -- Utility to List Device Vital Product Data (VPD)

control: owner -1 ! control: tags -1 moreinfo the same for libvpd applies here "License: GPL-2+ with librtas exception" maybe something like License: GPL-2+-with-librtas-exception is better (check lintian if complains) abort-upgrade|abort-remove|abort-deconfigure) ;; useless ^^ apt-get

Bug#826137: RFS: libservicelog/1.1.16-1 ITP: libservicelog -- Library to create and maintain a database for storing events

control: owner -1 ! control: tags -1 moreinfo Hi, the same for the other two libraries applies here, in addition: please run check-all-the-things, something should be fixed. g. Il Giovedì 2 Giugno 2016 18:06, Frederic Bonnard ha scritto: Package:

Bug#822856: Another try for dvtm?

Hi, still missing a build-dependency on libncurses5-dev the package just FTBFS http://debomatic-amd64.debian.net/distribution#unstable/dvtm/0.15-1/buildlog If it is ok for you I can add it, sign and upload. g. Il Mercoledì 25 Maggio 2016 21:03, Dmitry Bogatov ha scritto:

Re: [Debian-med-packaging] Trying to disable error=format-security for clapack

Hi Andreas, >o what I'd like to know: What's the difference between building the >code copy of libf2c comming with clapack (which can be proved by >deactivating use_debian_packaged_f2c.patch) and using libf2c2. (Bonus I would look at both build logs and gcc versions. maybe some new gcc

Re: [Help] Re: Bug#825461: staden: FTBFS in testing

Hi, some quick googling found some possible solutions https://www.google.it/search?client=ubuntu=fs=%22Scrt1.o%3A+In+function+`_start%27%3A%22=utf-8=utf-8_rd=cr=5ftHV7_JI8fA8geO-LmABQ I remember having that issue on ettercap some years ago, this is how I fixed it [1], but probably it was a

Re: Helping maintain debian packages

Hi, do you want something like this? http://mentors.debian.net/intro-maintainers G. Il Mercoledì 1 Giugno 2016 17:42, Marwan Rabbâa ha scritto: Hi, I have created a debian package https://packagecloud.io/waghanza/plunder/packages/debian/jessie/phantomjs_2.1.1_amd64.deb.

Bug#824104: RFS: gneural-network/0.9.1-1 [ITP]

control: tags -1 moreinfo Hi, as usual, I'm available for a new -science package, so I'll sponsor as soon as Ghislain is fine with the packaging. BTW I did a quick review, and it sounds fine to me I'm not sure about the multi-arch: foreign tag and about the lintian override: O: gneural-network:

Bug#826030: RFS: ntl/9.9.0-1 -- EXPERIMENTAL!

Hi, I uploaded the package on binnew queue. https://anonscm.debian.org/git/debian-science/packages/libntl.git/commit/?id=abd150f5fd1b277b7f47fb27c9c958f49d06a7ba I changed unstable to experimental, next time please don't forget that :) (BTW please check reverse-depends for buildability, open

Bug#820647: RFS: libretro-gambatte [ITP]

Hi Sérgio, can you please check the above/below and report back? I can do another check/review when you fix it. thanks, G. Il Sabato 21 Maggio 2016 19:36, Andrey Rahmatullin ha scritto: Control: tags -1 + moreinfo >From d/copyright, this is not distributable as it

Bug#825531: RFS: libcork/0.15.0+ds-1 [ITP]

Hi, >It's false positive. ack >> 2) lrwxrwxrwx root/root 0 2016-05-31 21:37 ./usr/lib/libcork.so.15 >> -> libcork.so.16.0.1 >The SONAME (15) and version (16.0.1) are given by upstream. >I guess it's also for legacy reason, to be compatible with other system. >So better not change by

Bug#825532: RFS: shadowsocks-libev/2.4.6+20160526+ds-1 [ITP]

Hi again, >It's false positive. ack >> Replaces: shadowsocks (<< 1.5.3-2) >> Breaks: shadowsocks (<< 1.5.3-2) > >Thanks to co-maintainer Boyuan, below comments are from him. > > >Upstream used to use the package name **`shadowsocks'** long long ago, >and the name was changed into

Bug#816968: RFS: broadcom-facetimehd/0.0.1~git20150229.1.8cc44d6 [ITP] -- DKMS driver for Broadcom PCIe cameras

Hi, I don't know if Nobuhiro wants to sponsor or not. In case a little additional review: arch: all? I don't think it is good to try to build dkms during build. the modules are useless anyway, and they have to be built during package installation (it might be good for an autopkgtestsuite).

Bug#820488: RFS: roadfighter/1.0.1269-1 [ITP] -- Drive a car in a death race

control: tags -1 moreinfo Hi, please fix the above/below, and maybe think about using pkg-games-devel to maintain that package (and ping back once you fixed that) cheers, G. Il Lunedì 23 Maggio 2016 15:03, Adam Borowski ha scritto: On Sun, May 22, 2016 at 02:07:39AM

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

control: owner -1 ! control: tags -1 moreinfo Hi, I tried to build and run, and (I admit, I'm behind a proxy) it failed with an error like runescape mv: cannot stat 'jagexappletviewer.jar': No such file or directory Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

Bug#816968: RFS: broadcom-facetimehd/0.0.1~git20150229.1.8cc44d6 [ITP] -- DKMS driver for Broadcom PCIe cameras

really attaching it :) g. Il Mercoledì 1 Giugno 2016 17:27, Gianfranco Costamagna <locutusofb...@debian.org> ha scritto: Hi, I don't know if Nobuhiro wants to sponsor or not. In case a little additional review: arch: all? I don't think it is good to try to build dkms during

Bug#820704: RFS: subuser/0.5.6-3 [ITP]

Hi, >On Mon, Apr 11, 2016 at 04:33:26PM +0200, Stanislas Leduc wrote: >> Upstream Author : [fill in name and email of upstream] >> * URL : [fill in URL of upstreams web site] >> * License : [fill in] >Huh? well, this is fixed in #820705 :) Stanislas, please fix and ping

Bug#819406: RFS: capitan/1.0.3-dfsg-1 [ITP] -- Remake of the classic 80s platform game

Hi, yes please fix the libpng build failure and the embedded libraries and I'll have another look here some hints about how to fix that https://titanpad.com/libpng16-transistion BTW general note: https://qa.debian.org/developer.php?login=pkg-games-de...@lists.alioth.debian.org pkg-games-devel

Bug#821151: RFS: comitup/0.1-1 [ITP]

control: owner -1 ! control: tags -1 moreinfo Hi, I can sponsor the package, lets see what needs fixing/answering: setup.py/install_requires is your friend, please use it, and drop the hardcoded runtime-dependencies using python:Depends (and check if everything is good) build and run: $ comitup

Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]

Hi, python-skimage should be RC free now (if no other RC bugs are opened of course :) ) let me know when you have updates, G.

Bug#827700: RFS: cplay/1.50-1 [NMU]

Hi, >The changes I have quoted above are not usually appropriate for NMUs. >In particular, changing from a version 1.0 to a 3.0 source package could >annoy the current package maintainers a great deal. > >In this case, it looks like those package maintainers are inactive (no >uploads since 2005).

Bug#827037: RFS: xpad/4.8.0-1 [ITA]

control: tags -1 pending > control: tag -1 +confirmed Hi Sean, thanks for the really nice review! I did sponsor on deferred/5, because I would like to have a feedback about the following >+ remove build-depends on libgtk2.0-dev, libmagickcore-extra, > autotools-dev, imagemagick.

Re: Bug#827487: bytes-circle_2.2-1_amd64.changes REJECTED

Hi Sean, >I think that we should avoid thinking that one purpose of source-only >uploads is to deal with DDs and DMs intentionally subverting security by >means of dodgy binaries. We already place a great deal of trust in >those who can upload packages, and it doesn't make sense to say that,

Bug#827082: RFS: libredjackipset/1.1.1+20150311-1 [ITP] -- C library to store sets/maps of IP address

Hi Roger >> cat debian/libcorkipset-doc.docs >> build-*/docs/html > >Debian builds obj- by default. >So it seems to specify "--builddirectory=build" safe for both debian and >ubuntu. yes, but useless... maybe you didn't get completely the hint, but my guess was: remove the --builddirectory

Bug#827090: RFS: runit/2.1.2-4 ITP

control: noowner -1 Hi, >actually I'm not okay with anyone taking over the runit packge. And I >don't see why runit needs an update in Debian. The few bugs are known >and can be worked around if necessary. well, updating the packaging is something I generally like a lot, it makes easier to

Re: how to build packages with a specific complier ?

Hi, >As far as I know, the plan is to switch to gcc-6 by default for stretch: >https://lists.debian.org/debian-gcc/2016/01/msg00100.html >so while identifying and backporting the fix to gcc-5 would be nice, I'd >recommend not putting too much effort there. fully agree, this is why I didn't

Bug#827082: RFS: libredjackipset/1.1.1+20150311-1 [ITP] -- C library to store sets/maps of IP address

Hi Roger, >Control: retitle -1 RFS: libcorkipset/1.1.1+20150311-1 [ITP] -- C >library to store sets/maps of IP address thanks for that! >I think you didn't review since you did last time, and I did some >changes based on some changes in previous post, so here I *rewrite* >the previous post.

Re: Bug#819395: RFS: stormlib-listfiles/2015-04-20-1 [ITP]

ter month, any news regarding this package? > > On Wednesday 27 April 2016 12:53:06 Gianfranco Costamagna wrote: > > Hi Pali and mentors, > > > > (redirecting the question to -mentors, because I don't have a > > strong opinion on this) > > > > >Looks like

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

Hi, >Added the "metadata" in d/upstream wonderful! >Sorry, I do not have programming skills in C and makefile. actually the "issue" is: -why did you create a c code that only starts a program? you can start it directly, with a bash script, as it was done before. I'm not sure having a program

Bug#827924: RFS: cplay/1.50-1 [QA] [RC]

control: owner -1 ! control: tags -1 moreinfo control: tags -1 pending Hi, I did a review, and uploaded on deferred/15 (please Peter and Jesus ack the changes or give a feedback about the QA upload if you aren't interested in the package anymore) with a little change. license seems really

Bug#827907: RFS: evil/1.2.12-1 ITP

control: owner -1 spwhit...@spwhitton.name yes, I did that ^^ :D and I have *no* regrets :p BTW I'm thrilled about bringing VIM to EMACS :D >I am looking for a sponsor for my package "evil" I think Sean can give a more appropriate review, but lets go: "make" in rules --> $(MAKE) please

Re: Proposing patch for packages, affected by transition

Hi, >Okay. But if they apply this patch right now, package will not build >aganist unstable. Is it okay? just mention that in the bug report, this will allow me/you to NMU when the transition starts >FAIL camldbm_1.0-2.dsc -- patch ready >FAIL courier_0.73.1-1.6.dsc >FAIL

Re: Proposing patch for packages, affected by transition

Hi Dmitry! >Recently, I took over gdbm package and got new version into >experimental. Now I work on fixing reverse dependencies FTBFS. > >Given I have patch for one of rdependency (camldbm, namely). What now? >Should I ask maintainer to apply it and make upload into experimental? >Or something

Re: Proposing patch for packages, affected by transition

Hi >> >Okay. But if they apply this patch right now, package will not build >> >aganist unstable. Is it okay? >> just mention that in the bug report, this will allow me/you to NMU when the >> transition starts > > >Okay. to be clear, NMU rules are the usual ones, e.g. NMU if no maintainer

Bug#824466: RFS: setop/0.1-1 [ITP]

Hi, Il Sabato 18 Giugno 2016 21:45, Frank Stähr ha scritto: >I think we are nearly ready, don’t give up. I *never* give up :) >Nevertheless, I don’t see why e. g. boost/algorithm/string/trim.hpp is >guaranteed to be installed. It might be a coincidence that it is

Bug#825532: RFS: shadowsocks-libev/2.4.6+20160526+ds-1 [ITP]

Hi Roger >Packaging another library (libipset) just takes some time. I can understand that, and my review will probably take some more time :) >Technically yes, but since it's a quite old version, I think nobody would do >it. >And currently "shadowsocks" is a python program in Debian archive,

Re: Help with python packaging

Hi >Get it fixed upstream. other than that, the manpage issue can be "probably" fixed by "PYTHONPATH=." before invoking help2man and of course using ./bin/codespell.py as argument oh, and I think manpage generation should be done in override_dh_installman, not dh_auto_build target. so,

Bug#827748: RFS: growl-for-linux/0.8.5-1

Hi, >I am looking for a sponsor for my package "growl-for-linux" LGTM Uploaded. G.

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

Hi, >Corrected the dependencies in d/control ack >Made to create a makefile. :/ but why? [Sergio Durigan Junion] > metadata stuff Sergio is correct, thanks! anyway, it seems working, so please answer the above and I'll do the final checks and hopefully upload. G.

Bug#827082: RFS: libredjackipset/1.1.1+20150311-1 [ITP] -- C library to store sets/maps of IP address

control: owner -1 ! control: tags -1 moreinfo Hi, lets see 1) control: why the -dev package is not multiarch? sounds like it is multiarch ready to me (I didn't check but include/* seems to have the same md5sum on different archs 2) the dev package should suggest the doc one 3)

Bug#827765: RFS: gdbm/1.12-2 ITP

Hi >I am looking for a sponsor for my package "gdbm" BTW not ITP :) (wrt message header) sponsoring in a few seconds, with a change s/UNRELEASED/experimental. G.

Bug#827398: RFS: pkg-kde-tools/0.15.21~bpo8+1

control: tags -1 moreinfo >I'm not sure whether you've coordinated this with the KDE team. I don't see >you among KDE packagers, and you haven't noted this in the RFS. NMU >backports are fine, but please say so if this is your intent. indeed, I'm tagging it moreinfo until this is sorted out

Bug#827082: RFS: libredjackipset/1.1.1+20150311-1 [ITP] -- C library to store sets/maps of IP address

Hi, >I think you build on ubuntu, so without "--builddirectory stuff" the >build directory is >build-*/ >When I tested in Debian, the build directory is obj-*/ >That's why I insist keeping "--builddirectory stuff" to make same >install file for both Debian and Ubuntu. nope, Ubuntu calls it

<    1   2   3   4   5   6   7   8   9   10   >