Hi list,
I found that in package qxmpp is used HTML documentation from upstream tarball.
This documentation was not generated by doxygen during build process. Should
I make a bug report? If yes, which section of Debian Policy I should point to?
Best regards,
Boris
--
To UNSUBSCRIBE, email to d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
*** UPDATE ***
New version from svn trunk (544~svn).
Documentation (html + LaTeX) is now included in build-process.
* Package name: libblocxx
Version : 544~svn-1
It builds those binary packages:
libblocxx-dbg - BloCxx debuggi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Severity: wishlish
*** UPDATE ***
New version from svn trunk (544~svn replaces 2.1.0).
Documentation (html + LaTeX) is now included in build-process.
Dear mentors,
I am looking for a sponsor for my package "libblocxx".
Have a loo
19.04.2012 12:30, Björn Esser пишет:
> Severity: wishlish
>
> *** UPDATE ***
> New version from svn trunk (544~svn replaces 2.1.0).
> Documentation (html + LaTeX) is now included in build-process.
>
> Dear mentors,
>
> I am looking for a sponsor for my package "libblocxx".
> Ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ok, so here we go again correcting the issues:
Severity: wishlish
*** UPDATE ***
New version from svn trunk (2.3.0~svn544 replaces 2.1.0).
Documentation (html + LaTeX) is now included in build-process.
Dear mentors,
I am looking for
Hi Paul,
On Thu, Apr 19, 2012 at 02:54:42PM +0800, Paul Wise wrote:
> On Thu, Apr 19, 2012 at 2:40 PM, Andreas Tille wrote:
>
> > The first question is: Why does it not find a new version at all:
>
> uscan relies solely on links and since there are no links to the
> tarballs, it cannot find any
On Tue, Apr 17, 2012 at 12:35 PM, Silvio Cesare wrote:
> The Debian Package clonewise-core (currently in the mentors archive)
> http://mentors.debian.net/package/clonewise-core
> http://www.foocodechu.com/downloads/clonewise
Here is a review of the package:
You should file an ITP bug:
http://ww
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Try something like:
version=3
http://www.bioconductor.org/packages/release/bioc/src/contrib/qvalue_([\d\.]+)\.tar\.gz
`wget
http://www.bioconductor.org/packages/release/bioc/src/contrib/qvalue_1.30.0.tar.gz`
works fine for me.
Cheers,
Björn Esse
This is interesting. is this related to
http://www.fossology.org/projects/fossology fosology in any way?
mike
On Tue, Apr 17, 2012 at 6:35 AM, Silvio Cesare wrote:
> The Debian Package clonewise-core (currently in the mentors archive)
> http://mentors.debian.net/package/clonewise-core
> http://ww
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ok, so here we go again correcting some issues:
*** UPDATE ***
New version from svn trunk (2.3.0~svn544 replaces 2.1.0).
Documentation (html + LaTeX) is now included in build-process.
Dear mentors,
I am looking for a sponsor for my
Hi,
I've updated the package which now installs the headers in a
subdirectory of /usr/include:
http://mentors.debian.net/package/gyoto
http://mentors.debian.net/debian/pool/main/g/gyoto/gyoto_0.0.2-1.dsc
Regards, Thibaut.
Le 16/04/12 17:10, Thibaut Paumard a écrit :
> Package: sponsorship-req
Eeek, I replied to the wrong bug. For the record, my review is here:
http://lists.debian.org/debian-python/2012/04/msg00078.html
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archi
Processing commands for cont...@bugs.debian.org:
> retitle 661507 RFS: libblocxx/2.3.0~svn544-1 [ITP] BloCXX--C++
Bug #661507 [sponsorship-requests] RFS: libblocxx/2.1.0-1 [ITP] -- BloCXX--C++
Framework for Application Development
Changed Bug title to 'RFS: libblocxx/2.3.0~svn544-1 [ITP] BloCXX--
Processing commands for cont...@bugs.debian.org:
> retitle 661507 RFS: libblocxx/2.3.0~svn544-1 [ITP] BloCXX--C++ Framework
Bug #661507 [sponsorship-requests] RFS: libblocxx/2.3.0~svn544-1 [ITP]
BloCXX--C++
Changed Bug title to 'RFS: libblocxx/2.3.0~svn544-1 [ITP] BloCXX--C++
Framework' from 'RF
On Thu, Apr 19, 2012 at 5:53 PM, Mike Dupont wrote:
> This is interesting. is this related
> to http://www.fossology.org/projects/fossology fosology in any way?
Unrelated. IIRC Fossology is mainly about looking at copyright and
license information. Clonewise is for automatically detecting embedd
Processing commands for cont...@bugs.debian.org:
> retitle 661507 RFS: libblocxx/2.3.0~svn544 [ITP] BloCxx - C++
Bug #661507 [sponsorship-requests] RFS: libblocxx/2.3.0~svn544-1 [ITP]
BloCXX--C++ Framework
Changed Bug title to 'RFS: libblocxx/2.3.0~svn544 [ITP] BloCxx - C++' from
'RFS: libblocxx
Processing commands for cont...@bugs.debian.org:
> retitle 661507 RFS: libblocxx/2.3.0~svn544 [ITP] BloCxx - C++ Framework for
Bug #661507 [sponsorship-requests] RFS: libblocxx/2.3.0~svn544 [ITP] BloCxx -
C++
Changed Bug title to 'RFS: libblocxx/2.3.0~svn544 [ITP] BloCxx - C++ Framework
for' fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The fixed and rebuild package has correctly uploaded to mentors now.
Am 19.04.2012 11:16, schrieb Björn Esser:
> Ok, so here we go again correcting the issues:
>
> Severity: wishlish
>
> *** UPDATE *** New version from svn trunk (2.3.0~svn544 repl
(message originally sent to the ITP instead of the RFS)
Hi,
Le 18/04/12 21:03, Jakub Wilk a écrit :
> (I don't intend to sponsor this package.)
Thanks for the comments nevertheless. I've fixed them all.
In the meantime, upstream succeeded in porting this extension to python
3, so I've updated th
On Thu, Apr 19, 2012 at 3:36 AM, Boris Pek wrote:
> Hi list,
>
> I found that in package qxmpp is used HTML documentation from upstream
> tarball.
> This documentation was not generated by doxygen during build process. Should
> I make a bug report? If yes, which section of Debian Policy I should
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
We are looking for a sponsor for our package "flactag"
* Package name: flactag
Version : 2.0.1-1
Upstream Author : Andy Hawkins
* URL : http://flactag.sourceforge.net/
* License : GPL v3
>> I found that in package qxmpp is used HTML documentation from upstream
>> tarball.
>> This documentation was not generated by doxygen during build process. Should
>> I make a bug report? If yes, which section of Debian Policy I should point
>> to?
>
> Well, there's nowhere in the DFSG or co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Boris!
I just investigated a bit inside the source-tar doing this:
cd doc
qmake
make
./doxyfilter -g
sed -i -e's/GENERATE_LATEX.*= NO/GENERATE_LATEX = YES/'\
- -e's/GENERATE_MAN.*= NO/GENERATE_MAN = YES/' ./Doxyfile
doxygen ./Doxyfile
cd ..
On Thu, Apr 19, 2012 at 9:18 AM, Boris Pek wrote:
>>> I found that in package qxmpp is used HTML documentation from upstream
>>> tarball.
>>> This documentation was not generated by doxygen during build process.
>>> Should
>>> I make a bug report? If yes, which section of Debian Policy I shou
Le 19/04/12 15:18, Boris Pek a écrit :
>>> I found that in package qxmpp is used HTML documentation from upstream
>>> tarball.
>>> This documentation was not generated by doxygen during build process.
>>> Should
>>> I make a bug report? If yes, which section of Debian Policy I should point
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As stated in my previous message, this is the way to generate the
needed Doxyfile:
cd doc (inside the tarball-basedir )
qmake ( produce Makefile )
make ( build ./doxyfilter )
./doxyfilter -g ( generates Doxyfile )
after this some sed-magic to enabl
Thanks all for answers.
I was searching for:
/doxyfilter -g
This command generates Doxyfile which is necessary for Doxygen.
> However I can't find anywhere in the Policy that it's an actual
> requirement to re-generate this kind of files at build-time.
So do I. That's why I've asked here should
Le Thu, Apr 19, 2012 at 03:57:59PM +0200, Thibaut Paumard a écrit :
>
> I believe it is generally accepted that every file that can be
> (re)generated during the build process should be, for various reasons.
Hi all,
I think that there is a consensus that generated files must be regenerable, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 19.04.2012 16:16, schrieb Boris Pek:
> Thanks all for answers.
You're welcome.
> I was searching for: /doxyfilter -g This command generates Doxyfile
> which is necessary for Doxygen.
>
>> However I can't find anywhere in the Policy that it's an
Le 19/04/12 16:20, Charles Plessy a écrit :
> Le Thu, Apr 19, 2012 at 03:57:59PM +0200, Thibaut Paumard a écrit :
>>
>> I believe it is generally accepted that every file that can be
>> (re)generated during the build process should be, for various reasons.
>
> Hi all,
>
> I think that there is a
Le 19/04/12 16:31, Björn Esser a écrit :
> Am 19.04.2012 16:16, schrieb Boris Pek:
>> Thanks all for answers.
>
> You're welcome.
>
>> I was searching for: /doxyfilter -g This command generates Doxyfile
>> which is necessary for Doxygen.
>
>>> However I can't find anywhere in the Policy that it'
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]
Dear mentors,
I am looking for a sponsor for my package "roxterm"
* Package name: roxterm
Version : 2.6.1-1
Upstream Author : Tony Houghton
URL : http://roxterm.source
Processing commands for cont...@bugs.debian.org:
> owner 669373 alger...@madhouse-project.org
Bug #669373 [sponsorship-requests] RFS: flactag/2.0.1-1 ITP #507876
Owner recorded as alger...@madhouse-project.org.
> tag 669373 + pending
Bug #669373 [sponsorship-requests] RFS: flactag/2.0.1-1 ITP #507
owner 669373 alger...@madhouse-project.org
tag 669373 + pending
thanks
Daniel Pocock writes:
> We are looking for a sponsor for our package "flactag"
>
> * Package name: flactag
>Version : 2.0.1-1
>Upstream Author : Andy Hawkins
> * URL : http://flactag.sourc
> I have a big collection of whole-album flacs, and would like to see this
> package in Debian, so I'll do a review and handle the upload (once
> blocking issues - if any - are fixed, of course).
>
Great - thanks for the prompt reply
Andy and I are lurking about in #flactag on irc.freenode.ne
On Thu, Apr 19, 2012 at 03:07:51PM +0200, Daniel Pocock wrote:
> flactag- Tagger for whole-album FLAC files using data from
> MusicBrainz
This is closing a fairly old (2008) ITP, so it might be good to re-evaluate
other software in the same space that is in Debian now -- particularly beets
On 19/04/12 20:41, Nicholas Breen wrote:
> On Thu, Apr 19, 2012 at 03:07:51PM +0200, Daniel Pocock wrote:
>> flactag- Tagger for whole-album FLAC files using data from
>> MusicBrainz
>
> This is closing a fairly old (2008) ITP, so it might be good to re-evaluate
> other software in the s
Hi,
I'm unsure whether this might be the proper mailing list to ask
questions like this - but I have no better idea.
I intend to parse some machine readable files in some team maintained
packages. When trying something like
ctrl = open('debian/control','r')
for ctrlstanza in deb822.Packag
Dear mentors,
please consider reviewing and sponsoring this new Rhinote upload.
As you can see from the changelog entry reported below, the updated package
contains several improvements that would make using Rhinote much better;
moreover, a Debian member has already reviewed the patches and found
On 04/13/2012 08:00 AM, Tobias Frost wrote:
Am Freitag, den 13.04.2012, 01:39 +0400 schrieb Michael Tokarev:
On 13.04.2012 01:08, Tomasz Muras wrote:
Hello,
A Debian developer has uploaded a NMU (moodle 1.9.9.dfsg2-5.1) to DELAYED/7-DAY
[1]. I have incorporated his changes, and added a new re
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for package "gammaray".
* Package name: gammaray
Version : 1.1.0-1
Upstream Author : Klarälvdalens Datakonsult AB
* URL : http://www.kdab.com/gammaray
* License : G
Hello,
I'm new on this list.
I plan to create a source package to build several binary packages (including
shell functions, shell scripts, udev rules and documentation). This will be a
Debian native package. My question is about the tarball, especially files
taking place outside of the debian/
Le Thu, Apr 19, 2012 at 05:02:13PM +0200, Thibaut Paumard a écrit :
> Le 19/04/12 16:20, Charles Plessy a écrit :
> >
> > I think that there is a consensus that generated files must be regenerable,
> > and
> > that it is a bug if their build system is broken. The best way to ensure
> > this
> >
Package: sponsorship-requests
Severity: normal
Package name: auralquiz
Version : 0.8.1
Upstream Author : Jan Kusanagi
URL : http://jancoding.wordpress.com/auralquiz/
License : GPL-2+
Section : games
It builds the single binary package 'auralquiz'.
To acce
"bilibop project" writes:
> I'm new on this list.
> I plan to create a source package to build several binary packages
> (including shell functions, shell scripts, udev rules and
> documentation). This will be a Debian native package. My question is
> about the tarball, especially files taking pl
Le 19/04/12 23:31, Tomasz Muras a écrit :
>
> Thanks for all the answers, I've uploaded updated package and NMU from
> the DELAYED queue got rejected because of the older version.
> I have kept the changelog entry from the NMU upload but what I didn't
> realize is that bugs closed by previous (NUM
46 matches
Mail list logo
