Hi Anton,
On Sun, Jul 10, 2011 at 02:52:48AM +0400, Anton Martchukov wrote:
> On Sat, Jul 09, 2011 at 02:57:20PM -0700, Hamish wrote:
> > +dfsg into version name:
> > as our build will be bit-for-bit identical to one built from a non-
> > stripped version of the source (the only difference between
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Michael,
On 07/10/11 05:03, Michael Tautschnig wrote:
> Hi,
>
> Sorry for taking so long for anyone to respond. Indeed this is a very nice
> example of making proper use of existing Debian packages, despite upstream
> shipping all the duplica
Hi Michael,
> Thanks a lot for updating your package. I've reviewed your changes and it
> looks
> mostly fine, except for one issue:
>
>>
>> Lintian run as "lintian -iIE --pedantic" gives the following output:
>>
>> W: mosquitto source: debhelper-overrides-need-versioned-build-depends
>> (>= 7.0.
>> Got it and found the package in the NEW queue.
>> http://ftp-master.debian.org/new.html
>>
>> It shows "source" and "i386" which is fine for (my) netbook(s).
>> I wonder though, will there be an amd64 package at some point?
>
> Packages get build for all architectures after they reach the arch
Hi again,
[...]
> > One suggestion for the package install procedure, though: why do you first
> > install all the files and afterwards remove them again via an override in
> > debian/rules? Wouldn't it be much cleaner to only install the desired files?
> >
>
> I preferred this method for a coup
On Sun, Jul 10, 2011 at 9:50 AM, Simon McVittie wrote:
> In my understanding of Policy and the DFSG, there's a difference between
> data not being built from source code, and data not being accompanied by
> source code at all.
>
> Data not *being built from* source code is a technical bug: it mean
Hi Roger,
[...]
> >> Lintian run as "lintian -iIE --pedantic" gives the following output:
> >>
> >> W: mosquitto source: debhelper-overrides-need-versioned-build-depends
> >> (>= 7.0.50~)
> > [...]
> >
> > Instead of copy-pasting this lintian warning, you should have addressed it
> > :-/ -
> > co
On Sat, 09 Jul 2011 at 18:34:09 -0700, Vincent Cheng wrote:
> Thanks for the review. Please also consider reviewing my most
> up-to-date packaging in the Debian Games svn repository; my Naev
> packaging at mentors.d.n is heavily outdated at the moment, mostly
> because I'm getting tired of having t
Hi,
> Dear mentors,
>
> I am looking for a sponsor for the new version 1.1.0.4+repacknot1-1
> of my package "assaultcube-data".
>
> It builds these binary packages:
> assaultcube-data - data files for AssaultCube
> assaultcube-server-anticheat - AssaultCube server with closed source
> anti-cheat
Hi Kilian,
Kilian Krause writes:
> Even though I've not found a debian/copyright info for *.png and *.desktop
> files I'll sponsor your package as is. Please try to clarify what license
> upstream intended for them (probably ISC too) and document that
> appropriately (or even better have them shi
Hi,
> Dear mentors,
>
> I am looking for a sponsor for my package "propel".
>
> * Package name: propel
> Version : 1.5.6-1
> Upstream Author : [fill in name and email of upstream]
> * URL : http://www.propelorm.org/
> * License : MIT License
> Section
Hi,
> I have updated my steadyflow package on mentors to the latest upstream
> version
> 0.1.7, based on the version of the package I got approved into Ubuntu
> Oneiric.
> I would be grateful if someone could review and sponsor the package.
>
> I'm upstream and a DM, and if I have the DM-Uplo
Hi Benoît
I am about to release a new version of jampal, and I have addressed most
of these issues (see below) in my latest debian build. However I still
have a couple of questions.
I am using wheezy/sid x86_64
This is the lintian report
lintian -I --pedantic *.dsc
P: jampal source: unneeded-build
On 2011-07-10 16:45, Peter Bennett wrote:
> Hi Benoît
>
Hi
> I am about to release a new version of jampal, and I have addressed most
> of these issues (see below) in my latest debian build. However I still
> have a couple of questions.
> I am using wheezy/sid x86_64
> This is the lintian report
The reason I added libappindicator-dev | hello was to avoid this
dependency being the only delta between Debian and Ubuntu. This way I'd
be able to sync from Debian into Ubuntu without changes. If that's flat
out unacceptable, I'll leave the dependency out and add it in Ubuntu
only until libappindi
> The reason I added libappindicator-dev | hello was to avoid this
> dependency being the only delta between Debian and Ubuntu. This way I'd
> be able to sync from Debian into Ubuntu without changes. If that's flat
> out unacceptable, I'll leave the dependency out and add it in Ubuntu
> only until
This is strange. I just tried building it in a sid pbuilder, and it
succeeded - in fact, I cannot reproduce this build error at all. Could
it be possible that you have vala-0.12 installed alongside some other
version of Vala (say, 0.10) and it's not the default version selected in
alternatives?
10
Hi Arno
Thanks for your comments. I am fixing the items you mention as well as
the ones from Benoît.
Which VCS links are you referencing in the control file? I am using the
sourceforge.net subversion for the debian files, is there a better choice?
I am cleaning up the descriptions for jampal and t
Hi,
> This is strange. I just tried building it in a sid pbuilder, and it
> succeeded - in fact, I cannot reproduce this build error at all. Could
> it be possible that you have vala-0.12 installed alongside some other
> version of Vala (say, 0.10) and it's not the default version selected in
> al
I've uploaded a new version to mentors, which patches the upstream build
system to use valac-0.12 as the executable name. Not very pretty, but
since we depend on the versioned package anyway, the version can always
be changed in both places.
11.07.2011 00:25, Michael Tautschnig wrote:
> I'm afrai
> I've uploaded a new version to mentors, which patches the upstream build
> system to use valac-0.12 as the executable name. Not very pretty, but
> since we depend on the versioned package anyway, the version can always
> be changed in both places.
>
Ok, looks good. Built & uploaded.
Thanks a l
Thanks for sponsoring!
Maia
11.07.2011 01:09, Michael Tautschnig wrote:
>> I've uploaded a new version to mentors, which patches the upstream build
>> system to use valac-0.12 as the executable name. Not very pretty, but
>> since we depend on the versioned package anyway, the version can always
>
I am hoping to understand the "obsolete" flag on conffiles in the dpkg
status file. There are many packages that include this flag at the
end of the line. For example:
Package: file
Conffiles:
/etc/magic.mime 272913026300e7ae9b5e2d51f138e674 obsolete
/etc/magic 272913026300e7ae9b5e2d51f138e674
On 2011-07-10 20:55 +0200, Bob Proulx wrote:
> I am hoping to understand the "obsolete" flag on conffiles in the dpkg
> status file. There are many packages that include this flag at the
> end of the line. For example:
>
> Package: file
> Conffiles:
> /etc/magic.mime 272913026300e7ae9b5e2d51f13
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.07.2011 18:21, Peter Bennett wrote:
> Hi Arno
> Which VCS links are you referencing in the control file? I am using the
> sourceforge.net subversion for the debian files, is there a better choice?
Please see [1]. The VCS should point to the vers
Hi,
> Hi!
>
> These packages are waiting for a sponsor:
> http://mentors.debian.net/debian/pool/main/q/qdacco and
> http://mentors.debian.net/debian/pool/main/d/dacco.
>
> This is a Catalan-English dictionary and a query GUI.
>
[...]
I've just uploaded dacco, looks good.
For qdacco, however,
Hi,
> Dear mentors,
>
> I am looking for a sponsor for my package "mgen".
>
> * Package name: mgen
> Version : 5.02-1
> Upstream Author : Naval Research Laboratory
> * URL : http://cs.itd.nrl.navy.mil/work/mgen/index.php
> * License : Open Source
> Section
Hi,
> This is again a request for a sponsor for JLDrill, a Japanese
> language learning tool. I'm not a Debian developer
> and have had some difficulty making good packages. I
> appreciate your patience! :-) This time I have removed the need for rake
> to build the debian package. I've left ru
Hi,
> Dear mentors,
>
> I am looking for a sponsor for my package "gogglesmm".
>
> * Package name: gogglesmm
> Version : 0.12.2-5
> Upstream Author : Sander Jansen
> * URL : http://code.google.com/p/gogglesmm/
> * License : GPLv3
> Section : sound
>
On 11 July 2011 06:09, Michael Tautschnig wrote:
> Just one more note, though: you don't even have filed an ITP for this package,
> which could also have drawn more interest to this package.
Hi Michael. Thanks for the response. Since I didn't get a response
for the RFP, I thought I would wait u
Hi,
I'm sorry, I haven't yet reviewed your package, I'm only commenting on the
issues you raised.
[...]
> It builds these binary packages:
> mosh - fast R6RS Scheme interpreter
> mosh-doc - reference documentation for Mosh
>
[...]
>
> #1. It requires an embedded copy of the Boehm GC.
Hi again,
> On 11 July 2011 06:09, Michael Tautschnig wrote:
> > Just one more note, though: you don't even have filed an ITP for this
> > package,
> > which could also have drawn more interest to this package.
>
> Hi Michael. Thanks for the response. Since I didn't get a response
> for the R
Hi Olaf,
> Dear mentors,
>
> I am looking for a sponsor for the new version 0.16-0.1
> of the package "taxbird".
>
> It builds these binary packages:
> taxbird- The first free Elster client (German Tax Declarations)
>
[...]
Could you please briefly explain why you are NMUing this package?
On 10/07/11 02:00, Michael Tautschnig wrote:
Hi,
[...]
Can you check the package again.
I've got a few questions concerning your changes, which aren't necessarily bugs,
but at least I'd like to see the rationale.
- The most recent policy version is 3.9.2; why did you update to 3.9.1 only?
Hi again,
[...]
>
> >Minor improvements to be made:
> >- You don't need to build-depend on quilt.
>
> I don't know how to solve it. I cannot found the build-depend.
>
Sorry, I meant the Build-Depends: entry in debian/control.
[...]
> >
> >Concerning your question for getting rid of binary-arc
Hi,
>> I am hoping to understand the "obsolete" flag on conffiles in the dpkg
>> status file. There are many packages that include this flag at the
>> end of the line. For example:
[...]
>
> They are obsolete because they no longer exist in the package. It is
> the package maintainer's task to
On Tue, 14 Jun 2011 17:39:50 +0200
Raoul Borenius wrote:
> Dear mentors,
>
> I am looking for a sponsor for my package "mgen".
>
> * Package name: mgen
> Version : 5.02-1
> Upstream Author : Naval Research Laboratory
>
> * URL : http://cs.itd.nrl.navy.mil/work/mgen/
The FLTK maintainer submitted a bug today to let me know that he's
created a change that will impact me:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633474
In the email, he attached a patch. I'm unsure of the best approach to
take for updating my package; I see three obvious choices:
1) Obvio
Gary Briggs writes:
> The FLTK maintainer submitted a bug today to let me know that he's
> created a change that will impact me:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633474
>
> In the email, he attached a patch.
Until upstream releases a new version with that patch applied, then it
On Mon, 11 Jul 2011 00:17:20 +0100, Michael Tautschnig wrote:
Hi again,
[...]
>Minor improvements to be made:
>- You don't need to build-depend on quilt.
I don't know how to solve it. I cannot found the build-depend.
Sorry, I meant the Build-Depends: entry in debian/control.
[...]
>
>Con
40 matches
Mail list logo
