Bug#798057: ITP RFS: node-sprintf-js/1.0.3-1

Control: owner -1 ! Control: tag -1 + moreinfo Salut Bastien, On Sat, 5 Sep 2015 00:17:01 +0200, Bastien ROUCARIES wrote: > I am looking for a sponsor for my package "node-sprintf-js" > > * Package name: node-sprintf-js >Version : 1.0.3-1 >

Bug#797888: RFS: panda3d/1.9.0-1 [ITP]

Hi everyone, I think everything is now ready for further work on the package. Thank you very much for your help! Regards

Re: Bug#797888: RFS: panda3d/1.9.0-1 [ITP]

Package: wnpp retitle 597172 ITP: panda3d -- Panda3D is a game engine, a framework for 3D rendering and game development for Python and C++ programs. thanks Hi Jörn, It seems your email client does line wrapping, so I am re-sending the retitle command. Usually line wrapping is good for

Bug#798057: marked as done (ITP RFS: node-sprintf-js/1.0.3-1)

Your message dated Sat, 5 Sep 2015 19:29:04 +0200 with message-id <20150905192904.2128a...@heffalump.lan> and subject line Re: Bug#798057: ITP RFS: node-sprintf-js/1.0.3-1 has caused the Debian Bug report #798057, regarding ITP RFS: node-sprintf-js/1.0.3-1 to be marked as done. This means that

What to do with a kernel bug which lets my package work result look bad ?

Hi, maybe somewhat off topic, but i don't know where else to ask for advise: While doing regression tests with my readily prepared packages (*), i stumbled over a bug in fs/isofs/rock.c which truncates filenames of length 254 or 255 to quite random lengths and thus can let readdir(3) emit

Re: What to do with a kernel bug which lets my package work result look bad ?

Report a bug (or if someone has already reported this against your package, reassign it) with Package: src:linux Control: affects -1 'affects' means it will appear in your package's bug list but be marked as linux's bug. (Example, now fixed:

Bug#798044: RFS: php-mf2/0.2.12-1 [ITP] -- Microformats2 is the simplest way to markup structured information in HTML.

Hi Bhuvan the packaging looks good to me, however I have some issues that you might want to address: 1) override_dh_install: dh_install well, this is funny and useless :) 2) no watch file is usually bad... please add one if possible 3) DH_VERBOSE in the rules file might be disabled, not an

Re: error adding symbols: DSO missing from command line

> Em 04/09/2015, à(s) 19:17, Craig Small escreveu: > > On Fri, Sep 04, 2015 at 08:33:52PM +0200, Jakub Wilk wrote: >> "help" is not a helpful subject. I updated it, so that is provides some >> context. > :) > Thanks. :) >> If you want people to help you, you need to make

Bug#798057: ITP RFS: node-sprintf-js/1.0.3-1

On Sat, Sep 5, 2015 at 1:41 PM, Stephen Kitt wrote: > Control: owner -1 ! > Control: tag -1 + moreinfo > > Salut Bastien, > > On Sat, 5 Sep 2015 00:17:01 +0200, Bastien ROUCARIES > wrote: >> I am looking for a sponsor for my package

Bug#797898: RFS: caffe/0.9999~rc2+git20150902+e8e660d3-1 [ITP]

On Fri, 2015-09-04 at 17:14 +, Gianfranco Costamagna wrote: > Hi again, > > The package doesn't build in a clean environment. > > http://debomatic-amd64.debian.net/distribution#experimental/caffe/0.~rc2+git20150902+e8e660d3-1/buildlog Well, I am surprised source Caffe suffers FTBFS on

Re: What to do with a kernel bug which lets my package work result look bad ?

On Sat, 05 Sep 2015, Thomas Schmitt wrote: > packages (*), i stumbled over a bug in fs/isofs/rock.c which > truncates filenames of length 254 or 255 to quite random > lengths and thus can let readdir(3) emit multiple identical > names in the same directory. Ugh. Yeah, that code looks broken at

Bug#798044: RFS: php-mf2/0.2.12-1 [ITP] -- Microformats2 is the simplest way to markup structured information in HTML.

Hi Gianfranco, Thanks a lot for reviewing the package I will do the necessary changes as suggested. I will make the upper case to lower too as suggested ;) Regards, Bhuvan On Sunday 06 September 2015 03:19 AM, Gianfranco Costamagna wrote: > Hi Bhuvan > > the packaging looks good to me, however

Re: Bug#797898: RFS: caffe/0.9999~rc2+git20150902+e8e660d3-1 [ITP]

Hi Gianfranco Costamagna, On Fri, 2015-09-04 at 17:04 +, Gianfranco Costamagna wrote: > if they aren't called by standard dh calls it is fine to keep them there. > > maybe just move to the bottom, (I think they are already there) I will keep those custom target in the bottom of d/rules.