-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors,
I am looking for a sponsor for the new version 1:0.92.1-1
of my package "gem".
It builds these binary packages:
gem- Graphics Environment for Multimedia - PureData library
The package can be found on mentors.debian.net:
- - URL
Dear Mentors,
I kindly request you to review the package gem:
http://mentors.debian.net/debian/pool/main/g/gem
It builds these binary packages:
gem- Graphics Environment for Multimedia - PureData library
Changes
- The package appears to be lintian clean.
- The upload would fix these b
hi all,
i finally have re-uploaded the new version of Gem, this time with
hopefully all the lintian warnings fixed, but one (see below).
Barry deFreese wrote:
> IOhannes m zmölnig wrote:
>> Dear mentors,
>>
>> I am looking for a sponsor for the new version 1:0.92.1-1
>> of my package "gem".
>>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2014-05-08 14:37, Nicolas wrote:
>> so why did you change dh compat-level from 8 to 9 then?
>>
>>
> I don't know exactly. There's no change that affect my package and
> the others packages I work on used compat level 9
that's a rather lame reas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2014-05-12 04:33, Paul Elliott wrote:
> But is there some kind of work around that will let you keep
> working somehow?
depends on what you mean by "working".
a) the sid machine is your primary computer, where you do all kind of
things (not only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-01 07:07, Guo Yixuan wrote:
> Hello everybody,
>
> I uploaded a packge, gcc-doc-defaults, which closes some bugs of
> gcc-doc (a binary package built from src:gcc-doc-defaults).
> However, mentors.debian.net displays an error: "Package clos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-08-11 10:50, Asheesh Laroia wrote:
>
> Okay!
>
> As of Thu Aug 11 08:47:29 UTC 2011, mentors.debian.net now runs the
> Debexpo code.
thanks to asheesh (with big cheers) for doing all the work.
i really appreciate it.
i believe that the few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors, sponsors and fellow Debianistas,
I am looking for a sponsor for my package "assimp".
* Package name: assimp
Version : 2.0.863~dfsg-1
Upstream Author : ASSIMP Development team
* URL : http://assimp.sf.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear mentors, sponsors and fellow Debianistas,
here is my third attempt to find a sponsor (or more reviewers) for my
package "assimp".
since the main package description has not really changed much since
last friday, i will give you just a quick over
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-08-23 20:55, Vincent Cheng wrote:
> On Tue, Aug 23, 2011 at 11:19 AM, Jan-Hendrik (hennr) Peters
> wrote:
>> But there is another lintian warning that bugs me and I could use some
>> advices with this one:
>> W: flare: executable-not-elf-or-sc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-09-20 09:14, Godfrey Chung wrote:
> I would be glad if someone uploaded this package for me.
>
according to
http://packages.qa.debian.org/a/acsccid/news/20110818T224710Z.html, this
package has already been uploaded two days ago :-)
but maybe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-09-20 10:26, Godfrey Chung wrote:
> Dear IOhannes
>
> My package is 1.0.2-3 and not 1.0.2-2.
>
oops, sorry about that.
i checked and double checked before writing the email, but obviously was
unprepared that the mentors.d.n would give me bot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i was wondering, what is the best way to *exclude* files from a package
that get installed by upstream's "make install" target?
at the same time i don't want to miss the comforts of packaging systems
like cdbs.
e.g. upstream uses autotools as bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-10-13 02:10, Charles Plessy wrote:
>
>> - - removing the files right after the "install" target.
>
> Dear IOhannes,
>
> I tend to exclude files by removing them. This way, it is self-documenting
> (but a comment on why they are removed may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-21 21:58, IOhannes m zmoelnig wrote:
> hi all,
>
>
> i'm currently in the process of splitting a package i'm co-maintaining
> into several sub-packages.
>
> unfortunately i experience some problems with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi all,
i'm currently in the process of splitting a package i'm co-maintaining
into several sub-packages.
unfortunately i experience some problems with test upgrades, which i
would like to solve.
the original package "gem" has been split into "gem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-21 23:25, Jakub Wilk wrote:
>> hmm, i only now realized that my package actually uses an epoch, so it
>> should read "<< 1:0.93", but this doesn't seem to help either.
>
> It should help. Are you sure that you corrected versions in both Bre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ola,
i have a question regarding one of the packages i'm co-maintaining
("puredata", a graphical realtime computer music language).
when "puredata" was packaged first (~1999), this was done under the name
of "pd".
later it has been re-named to "pured
18 matches
Mail list logo
