Thank you for all your comments.
I will come back later with a new upstream release, especially for the
font rendering which requires big changes. That was probably something
to be done anyway, since I guess it would improve the font rendering
quality which I was not too happy about.
For the rest
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my application filebot
Package name: filebot
Version : 3.1
Upstream Author : Reinhard Pointner redn...@users.sourceforge.net
URL :
Dear all,
I'm currently staring with packaging some software (initially intended
for debian-med) and amongst these packages is a software library with
its Doxygen created documentation.
Doxygen created a jquery.js script that depends somehow on the options
used to run the document creation
Hi Doug,
The file wmtime_1.0b2.orig.tar.gz at mentors is not identical to the one in
Debian. What is debian/0001-Packaging-for-Debian.patch for ? The changelog
entry of 1.0b2-13 Rebuilding source package correctly is not useful if you
didn't change the source package. The homepage in the
On 11/24/2012 01:54 AM, Gert Wollny wrote:
Now I've seen that Doxgen has the jquery-1.3.2.js file in the debian/
directory and in fact with this script the pages display correctly. My
question is now, should I also include this source file in the source
distribution, or would it suffice to
Thomas Goirand z...@debian.org writes:
On 11/24/2012 01:54 AM, Gert Wollny wrote:
Now I've seen that Doxgen has the jquery-1.3.2.js file in the debian/
directory and in fact with this script the pages display correctly. My
question is now, should I also include this source file in the source
On Fri, Nov 16, 2012 at 07:49:46AM -0600, John Hasler wrote:
None of these bugs (or any bugs above normal) apply to the version of
Chrony in Sid. They could all by fixed by migrating that version (the
current upstream release) to Wheezy but as it is frozen that is not
possible unless the
Hello Enrico,
Enrico Zini wrote on 2012-11-23 22:23:
So please do not consider the ball to be in the release team's court:
for this to be fixed, the relevant changes need to be backported to
1.24.
I am on the way to upload a new chrony version 1.24-3.1+deb7u1
as David Prévot wrote on
Hello!
What is the right way, if a bugreport were closed with the newest sid
version because this bug were fixed in this sid version, but the same bug
is not fixed in freezed testing/wheezy version?
Example:
Found in version testing-version
Fixed in version sid-version
Done: ...
On Fri, 23 Nov 2012, Joachim Wiedorn wrote:
Can this bug report be closed especially for version 1.24-3.1 by
writing the bug report number in the changelog a second time -
automatic done?
Yes. Multiple -done mails with version pseudoheaders are handled
properly by the BTS.
Or is the only
On Sat, Nov 17, 2012 at 10:07 PM, Michael Gilbert wrote:
The following look like they'll be pretty easy, so they're a prime
opportunity for mentees to build, test, and prepare a package to be
potentially sponsored:
So, it's been almost a week, and I decided to take a look at where
things stand
On Fri, Nov 23, 2012 at 7:28 PM, Michael Gilbert wrote:
On Sat, Nov 17, 2012 at 10:07 PM, Michael Gilbert wrote:
The following look like they'll be pretty easy, so they're a prime
opportunity for mentees to build, test, and prepare a package to be
potentially sponsored:
So, it's been almost
Processing commands for cont...@bugs.debian.org:
retitle 693495 RFS: wmtime/1.0b2-14 [ITA]
Bug #693495 [sponsorship-requests] RFS: wmtime/1.0b2-13 [ITA]
Changed Bug title to 'RFS: wmtime/1.0b2-14 [ITA]' from 'RFS: wmtime/1.0b2-13
[ITA]'
stop
Stopping processing here.
Please contact me if you
On Fri, Nov 23, 2012 at 10:56:20PM +, Doug Torrance wrote:
bartm wrote on 23 Nov 2012 17:54 :
The file wmtime_1.0b2.orig.tar.gz at mentors is not identical to the one in
Debian. What is debian/0001-Packaging-for-Debian.patch for ? The changelog
entry of 1.0b2-13 Rebuilding source
14 matches
Mail list logo
