Alexander Reichle-Schmehl writes:
> Am 19.01.2012 12:26, schrieb Arno Töll:
>> On 19.01.2012 05:32, Michael Gilbert wrote:
Second concern i have here is that (AFAIK) everyone can upload
everything to mentors.debian.net. Which would mean we then would/could
distribute non-distribite
Paul Elliott writes:
>> http://wiki.debian.org/Alioth/PackagingProject
>> Source: libswe
>> Version: 1.77.00.0004-1
>> Severity: serious
>> Justification: fails to build from source
>>
>> Automated builds of libswe are failing because unoconv (used to
>> produce PDF and HTML documentation) assum
Marco Balmer writes:
> Upstream author announced a new version 0.3.1 which is packaged now:
> dget -x
> http://mentors.debian.net/debian/pool/main/c/couriergrey/couriergrey_0.3.1-1.dsc
After a couple of last-minute updates, this is now sitting in NEW.
--
|8]
--
To UNSUBSCRIBE, email to deb
Mathieu Malaterre writes:
> So here is what I ended up doing:
>
> $ cat rules
> ...
> override_dh_auto_configure: check-mono-archs
> ...
> mono_archs=$(DEB_MONO_ARCHS)
> gdcm_archs="$(shell grep -2 libvtkgdcm-cil debian/control | grep
> Architecture | cut -d: -f2 | tr " " "\n" | sort -g)"
> mono_
Marco Balmer writes:
> Changes since the last upload:
>
> couriergrey (0.3.1-2) unstable; urgency=low
>
> * d/couriergrey.cron.daily: Fix failed cron job if package was in
> uninstall and not purge state.
>
> -- Marco Balmer Thu, 02 Feb 2012 08:06:19 +0100
I have reviewed the changes, a
"Stephen M. Webb" writes:
> On 02/07/2012 08:15 AM, Vincent Hobeïka wrote:
>>
>> [1] :http://mentors.debian.net/debian/pool/main/v/vera++/vera++_1.1.1-3.dsc
>> [2] :http://mentors.debian.net/package/vera%2B%2B
>
> How did you build that source package? It has a diff.tar.gz file but no
> debian.
debian-de...@liska.ath.cx (Olе Streicher) writes:
> There is another version of this library available, where the (C)
> sources are available (and put under GPL), but obfuscated, so that they
> cannot go into "main" but would have to go into "non-free". However, I
> am thinking about packaging thi
debian-de...@liska.ath.cx (Olе Streicher) writes:
> Björn Esser writes:
>> So I'd suggest name the free one slalib and the other one
>> slalib-nonfree or vice versa (like the unrar example).
>
> The problem is that I want the dependent programs to be linked against
> any of them.
>
> For example
debian-de...@liska.ath.cx (Olе Streicher) writes:
> Gergely Nagy writes:
>> debian-de...@liska.ath.cx (Olе Streicher) writes:
>>> For example "saods9" would use slalib as a shared library, and I want to
>>> git the user a choide to run it either with the f
Jakub Wilk writes:
> * Ben Finney , 2012-02-13, 13:40:
>>> I want to keep trace of it in the d/changelog by keeping my first
>>> version entry and adding a second entry. Can I do that ? Will it
>>> confuse some Debian robots ?
>>
>> It's fine. I consider uploading the package to ‘mentors.debian.n
Boris Pek writes:
> Hi,
>
>> Personally, I like the middleground best (though, I haven't been
>> practicsing this yet, but this is how things would work in my ideal
>> world): upload to mentors.d.n with incremental versions (when it makes
>> sense; if the reviewer/potential sponsor spots a bug in
Boris Pek writes:
>> Depends on the situation. If it's a quick update, and I can followup
>> within moments, then indeed, there is no reason to increment the version
>> (see my "when it makes sense" comment above).
>>
>> But if hours, or even days can pass between iterations, then I much
>> prefe
Nicolas Dandrimont writes:
> Le 13/02/2012 à 13:14, Gergely Nagy écrivit :
>>
>> ${VERSION}-${N}~mentors${X} for mentors, ${VERSION}-${N} for Debian
>> proper. A little more work on both sides, but we get the best of both
>> worlds with as little of the worst as
fre...@free.fr writes:
> What I especially like to know if this should be group-writable, but
> maybe it's not important.
They should not be. There is no reason to use anything but 644/755,
respectively.
--
|8]
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subjec
Arno Töll writes:
> Except debehelper in compatibility mode 9. There, debhelper
> configuration files can be scripts (as you know), which are determined
> by the +x bit.
That's covered by 755. But executable dh files are not for the faint of
heart, nor for beginners who need to ask these questio
Jerome BENOIT writes:
> Hello List:
>
> What should be the default target for debian/rules ?
I usually make a help target (or something similar) and make that the
default. But now that you reminded me, I always wanted to make it
display debian/README.source, so I'll just do that for my packages.
Dmitry Smirnov writes:
> Could any of you share experience of having your own private build server?
>
> I'm thinking of something which could build uploaded source for as many
> architectures as possible on amd64 host, and ideally put the results to
> 'reprepro'-managed tree.
>
> The goal is t
Samuel Bronson writes:
> It's getting to the point where I think it would be best if we do one
> of two things:
>
> 1. Split out sponsorship-requests bug mail to a new mailing list.
>
> 2. Stop sending it anywhere, and let people subscribe through the PTS
> if they care.
>
> How about you?
I'd
Thomas Goirand writes:
> On 03/13/2012 06:18 PM, Gergely Nagy wrote:
>> I would also love to see a "Review & Mentor" team, something that could
>> work along and with the NM process, whose task would be to do just what
>> the name suggests: reivew packages, he
Ben Finney writes:
> What is the recommended way to specify packaging for a library package
> and its corresponding debug symbols package?
I use the following line at the top of my debian/rules:
export DH_OPTIONS += --dbg-package=foo-dbg
This appears to do the right thing with dh compat level
Ross Boylan writes:
> Short version:
>
> What's the best way to work with a dpatch-based package developing code
> that will likely take many smallish iterations to get right?
As the other reply said: the best way is not to.
The long version of the same answer: dpatch is not a VCS, was never
me
Andreas Tille writes:
> Hi,
>
> I would like to add man pages to a program which does not accept any
> help option but if you call it without any option it outputs the help
> information which would be needed to create the man page. Is there
> any trick to convince help2man to work on this anywa
On Mon, Apr 2, 2012 at 00:29, David Prévot wrote:
> Hi,
>
> Le 01/04/2012 18:24, Gergely Nagy a écrit :
>> Andreas Tille writes:
>
>>> I would like to add man pages to a program which does not accept any
>>> help option but if you call it without any option
Ross Boylan writes:
>> Which, in this case, probably means running debian/rules build over and
>> over again, until you have something that works.
> I thought debian/rules build would invoke the same patch logic, but I
> tried it and it didn't. Thanks for the tip.
It won't, because unpatching
Mathieu Malaterre writes:
> Hi mentors,
>
> I am starring at the buildd status page of mrmpi:
>
> https://buildd.debian.org/status/package.php?p=mrmpi
>
> I cannot make any sense of the results on armel, armhf, i386, ia64,
> mips and powerpc. Why are those arch running *-indep rules ?
They a
I had a look at this request, but sadly, the debdiff did not apply:
$ patch -p1 <663685.debdiff
patching file debian/rules
Hunk #2 FAILED at 21.
1 out of 2 hunks FAILED -- saving rejects to file debian/rules.rej
patching file debian/control
patching file debian/changelog
patching file debian/READM
Matt Zagrabelny writes:
> On Wed, Apr 4, 2012 at 9:49 AM, Matt Zagrabelny wrote:
>> Greetings,
>>
>> I am packaging up milter-regex. The upstream source has three makefiles:
>>
>> Makefile
>> Makefile.linux
>> Makefile.solaris
>>
>> The file, "Makefile", is for building in a BSD environment. If
Vladimir Stavrinov writes:
> On Wed, Apr 04, 2012 at 09:11:03PM +0200, Didier Raboud wrote:
>
>> Debian already has one component named the Debian Installer [0,1], which is
>
> As usual, I was not satisfied with it and hence wrote my own installer
Out of curiosity, what were your problems with
Matt Zagrabelny writes:
> Thanks for the hint, Gergely. Unfortunately the man page, in
> particular the EXAMPLES section, does not address my *initial*
> question (AFAIK):
>
> ---{original question}---
> Is there an easy way to tell "dh" that it should
> use Makefile.linux instead of Makefile?
>
Vladimir Stavrinov writes:
> On Wed, Apr 04, 2012 at 01:39:07PM +0300, Timo Juhani Lindfors wrote:
>
>> I think rpg is very insecure since all local users of the system can see
>> the passwords that you generate. All they need to do is to look for the
>> "grep" commands that appear in the process
debian-de...@liska.ath.cx (Olе Streicher) writes:
> $ ls -l msgs/
> insgesamt 308
> -rw-rw-r-- 1 ole no 39129 2012-04-11 14:01 da.msg
> -rw-rw-r-- 1 ole no 38259 2012-04-11 14:01 de.msg
> -rw-rw-r-- 1 ole no 41958 2012-04-11 14:01 es.msg
> -rw-rw-r-- 1 ole no 37107 2012-04-11 14:01 fr.msg
> -rw-rw
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
"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
Paul Elliott writes:
> It has been suggested by a respected reviewer that while I am removing the
> unsourced binaries, I remove ALL of the "convenience copies of code". That
> way
> the unused code would not confuse anyone.
>
> I thought, that when creating a dfsg tarball, one should remove o
Tomasz Muras writes:
> On 04/22/2012 02:48 PM, Bernhard R. Link wrote:
>> * Arno Töll [120421 11:51]:
>>> The whole point of a changelog is a time dependent frozen point of view
>>> at your package. Once you released a version of a package, you should
>>> consider it untouchable
>>
>> I strongly
karunakar medamoni writes:
> cp: cannot stat `debian/tmp/usr/share/XAwu': No such file or directory
> dh_install: cp -a debian/tmp/usr/share/XAwu
> debian/xawu/var/www/htdocs/XAwu/ returned exit code 1
> make: *** [binary-install/xawu] Error 2
A bit more information would be appreciated. Where d
Whit Armstrong writes:
> Thanks, Daniel.
>
> I would be looking for 6-64999, assuming my package eventually
> made it into debian, I suppose it would need to have a 'globally
> allocated' uid. The idea is simply not to give users executing an R
> script on the machine root access.
Why do yo
Whit Armstrong writes:
> Matt, Ansgar, and Gergely,
>
> Thanks for the tips.
>
> Can you also help with some advice on the init.d script?
>
> The init.d script for deathstar launches a daemon which listens for
> jobs, and one worker per core.
>
> Can I use the same pid file for all of those proce
Whit Armstrong writes:
>> I assume it has a main process, which when stopped, would result in the
>> workers being killed too. If that is so, I do not think you need to
>> store the pids of the workers anywhere.
>
> Perhaps I'm confusing terminology here. The main deamon does not
> spawn the wor
Andy Hawkins writes:
> Hi,
>
> In article
> <87wr5bbt4i.fsf__16851.6493672088$1334852129$gmane$org@algernon.balabit>,
> Gergely Nagy wrote:
>> owner 669373 alger...@madhouse-project.org
>> tag 669373 + pending
>> thanks
>>
>> D
reassign 671476 sponsorship-requests
severity 671476 wishlist
thanks
nick black writes:
> Package: rfs
> Severity: normal
When filing RFS bugs, please follow the guidelines[1], and file it
against sponsorship-requests, with the appropriate severity (wishlist
for new packages).
I have reassigne
debian-de...@liska.ath.cx (Olе Streicher) writes:
> Dear Mentors,
>
> For a package [1], I have to patch one file (Makefile.am) twice: once
> from debian/patches, and the other times from debian/rules. The patch in
> debian/patches is needed to bring allow the use of a standard automake
> (upstrea
Daniel Pocock writes:
> Why the confusion? The old package is named after the ABI number in
> SONAME, the new one is named after the code version.
>
> Both Debian packages are called libmusicbrainz4, yet
> OLD: code v2.1.x, SONAME = libmusicbrainz.so.4, ABI = 4
> NEW: code v4.0.x, SONAME = libmu
Hi!
I'd suggest we keep this to the bugreport, no need to Cc mentors:
whoever is interested, can post to the bug.
I haven't reviewed the whole bug log yet, but one part caught my attention:
On Mon, May 14, 2012 at 5:58 PM, Andrew Shadura wrote:
>> > > * You should also consider using DEP5 for
noowner 669373
tag 669373 - pending
thanks
Andy Hawkins writes:
> Gergely, Daniel has uploaded new packages for flactag (2.0.2-1) and
> libmusicbrainz5 (5.0.1-1). Are you still considering sponsoring flactag?
> Would you also consider sponsoring libmusicbrainz5? Now that its version
> number has
Andy Hawkins writes:
> Hi,
>
> In article ,
>Debian Bug Tracking System wrote:
>> Processing commands for cont...@bugs.debian.org:
>>
>>> noowner 669373
>> Bug #669373 [sponsorship-requests] RFS: flactag/2.0.2-1 ITP #507876
>> Removed annotation that Bug was owned by alger...@madhouse
Arno Töll writes:
> What about creating a list as owner of the pseudo-package dedicated to
> BTS traffic (including control messages) named
> sponsorship-requests@l.d.o. Furthermore, the mentors list should still
> get bug traffic (only). Therefore we would subscribe that list via PTS
> subscript
Julian Wollrath writes:
> David Bremner wrote:
>> This kind of change (changing the copyright file format) is not usually
>> acceptable in an NMU, unless cleared with the maintainer.
> But how else should I address the missing license information for 'pevent/*',
> 'src/perf/perf_event.h', 'src/
Bas van den Dikkenberg writes:
> Hello,
>
> I am trying to make burp work on HPPA and powerpcspe architectures and
> there for I want to specify witch version of debhelper he must juse.
You're trying to do the wrong thing: debhelper is arch:all, so it will
be the same across architectures. If yo
Arno Töll writes:
> Hi,
> Jakub asked me to forward his comment from IRC to thhis list (where he's
> not subscribed anymore as some might remember):
>
> 14:14 < jwilk> IME the problem with mailing lists that nobody reads is
> that from time to time some misguided people will post to them. Worse,
Björn Esser writes:
> Hello!
>
> Why does dh >= 9 (in paticular the latest version in sid) put the
> debugging-symbols in
> usr/lib/debug/.build-id/$(2-Byte-Random)/$(Random).debug when building
> a lib with multi-arch-support?
See #642158, for an explanation. The short story is, it's easier to
Faré writes:
> Dear mentors,
>
> I am looking for a sponsor for
> the new version 2:2.22-1 of my package "cl-asdf".
Is there an easily accessible changelog to see what changed in 2.22-1
since the last upload? (VCS-Browser could work too, but a .changes file
would be nice. Alternatively, pasting
Don Armstrong writes:
> On Wed, 13 Jun 2012, Ansgar Burchardt wrote:
>> No, as far as I know the current plan was to change the maintainer for
>> the pseudo-package and then subscribe -mentors@ to only the discussion
>> part via the PTS (the "bts" keyword there, but not "bts-control").
>
> Ah; I
Christophe-Marie Duquesne writes:
> I am the author of an opensource library that reimplements a
> closed-source library.
[...]
> PS: the project in question is more a "proxy" towards the closed
> source library than a real reimplementation, but technically I
> actually reimplement every function
Christophe-Marie Duquesne writes:
> On Fri, Jul 6, 2012 at 2:40 PM, Roger Leigh wrote:
>> To avoid any implication that anything from the headers has been
>> copied, why not just use the output of "nm [-D]". This is the
>> interface that programs use to link with the library, and is
>> what you
Andreas Rönnquist writes:
> I believe you have greater chances getting an answer to this on
> debian-mentors@lists.debian.org - list CC'd.
Actually, no, not really. The debian-mentors@ list is for Debian
packaging, mostly, not for questions unrelated to that. I'd think -user
or http://ask.debian
Bart Martens writes:
> Is it OK that a sponsor adds modifications to a sponsored package ?
Under certain conditions, it can be ok. An OK from the sponsoree is one
such condition.
> Is it OK that a sponsor adds him/herself to "Uploaders" ?
Again, with the sponsoree's agreement, and if the spons
"Daniele E. Domenichelli" writes:
> Hello Andreas,
>
> On 16/07/12 16:15, Andreas Tille wrote:
>> Could you try to implement this to enable me building with
>> git-buildpackage easily?
>
> git-buildpackage should be fixed now, but I didn't import the pristine
> tar, since it is exactly the same a
Rustom Mody writes:
> I use and am interested in packaging the C interpreter
> http://www.linuxbox.com/tiki/node/149
> 1. Its not under GPL but a 'creative licence'
>From the homepage, and the source, this 'creative license' appears to be
the Artistic License, used by, for example, Perl. I do n
Benoît Knecht writes:
> Hi Albert,
>
> Albert Huang wrote:
>> I am looking for a sponsor for my package "tilem"
>>
>> * Package name: tilem
>>Version : 2.0-1
>>Upstream Author : Benjamin Moody and Thibault Duponchelle (
>> tilem-de...@sourceforge.net)
>> * URL :
"BRAGA, Bruno" writes:
> The "hack" I am doing to get this working is to basically to alter the main
> package bash_completion file, which is created with a variable prepared to
> be tempered with by plugin installations:
>
> ...
> opts="option1 ... optionN"
> plugin_opts=
> ...
Would it not be
packages in my personal repository,
reportbug from squeeze does the right thing (I assume it works similarly
in wheezy and sid too, I didn't test):
,
| algernon@galadriel:~$ reportbug syslog-ng-core
| Warning: no reportbug configuration found. Proceeding in novice mode.
| Detected charac
Toni Mueller writes:
> On Tue, 31.05.2011 at 14:59:25 +0300, Andriy Senkovych
> wrote:
>> I'm an uploader of the buildbot and buildbot-slave Debian packages and
>> a contributor to the buildbot project[1] itself. As you may wonder,
>> buildbot is a distributed continious integration tool writte
Kilian Krause writes:
> 1. Using dh-autoreconf is ugly. Please try to avoid it and backport the
> full regenerated configure in your patch to make sure the source is
> identical on all buildds. IMHO dh-autoreconf is a solution for a local
> build that you maintain for yourself outside of Debian, b
Hi!
While I'm not looking for a sponsor for my package, git-flow, I would
appreciate any comments regarding the packaging, and all ideas for
improvement.
* Package name: git-flow
Version : 0.4.1-1~preview0
Upstream Author : Vincent Driessen ,
Kate Ward,
Thomas Goirand writes:
>> On Fri, Jul 08, 2011 at 12:55 +0200, Jakub Wilk wrote:
>>
>> [...] but should be made explicit as the reasons not to use dh, for
>> example, might mean that the helper is lacking functionality or
>> behaves buggy in certain situations.
>
> I don't get it here...
>
> D
Thomas Goirand writes:
> On 07/09/2011 05:14 AM, Gergely Nagy wrote:
>> I believe that when someone knows the underlying system, using helpers
>> is the way to go, because it makes not only your task easier, it also
>> makes it easier for others to understand the packa
> But I still want to fix the .symbols file. However, I was not able to
> find how I should do it in this case (new packagename).
> Should I just generate a new file from scratch (I have not seen
> incompatible api changes) or refer to the old version number for
> functions which were available bef
Hi!
Kilian Krause writes:
> On Fri, Jul 08, 2011 at 11:34:18AM +0200, Gergely Nagy wrote:
>> While I'm not looking for a sponsor for my package, git-flow, I would
>> appreciate any comments regarding the packaging, and all ideas for
>> improvement.
>>
>>
Tony Houghton writes:
> I'm pretty sure I once read something about how to get a single source
> package to build multiple binary packages from the same source with
> different configure options. Unfortunately I can't remember what I read
> and it didn't apply to dh anyway. Can anyone recommend a
Didier Raboud writes:
> I'm doing it slightly differently, using the --builddirectory parameter of
> dh:
Yeah, that's pretty much the same thing, with a bit better style =)
> And add rm -rf build-* to override_dh_auto_clean.
Right, this part I completely forgot to mention. Thanks!
--
|8]
Tony Houghton writes:
> Yes, I'm using the short form.
>
> Thanks to everyone who showed me how to do this. But I'd also appreciate
> some feedback on the question of whether it's sensible to provide two
> versions of roxterm this way or should I pick one version and stick to a
> simple rules fil
Asheesh Laroia writes:
> Excerpts from Antonio Valentino's message of Sat Aug 13 07:09:57 -0400 2011:
>> Hi mentors,
>> I have a package (pyepr) that provides a small python extension written
>> in cython.
>> The upstream source includes a test suite that needs some data to be
>> downloaded from
Oohara Yuuma writes:
> I am packaging a software which uses autoconf and automake. I will
> regenerate all autotool files with dh-autoreconf.
> * The upstream tarball contains auto-generated files. Do I have to
> save these files somewhere before calling dh_autoreconf and restore
> them in
Jakub Wilk writes:
> * Gergely Nagy , 2011-08-16, 16:16:
>>>I am packaging a software which uses autoconf and automake. I will
>>>regenerate all autotool files with dh-autoreconf.
>>>* The upstream tarball contains auto-generated files. Do I have to
>>> sa
Jean-Philippe MENGUAL writes:
> I'm not sure of release number, but I put -2 as -1 was
> the NMU and I didn't want to remove this.
Since the NMU never hit the archive, and -1 is not an NMU version number
anyway, I'd merge the two changelogs into one.
Also, looking at the changelog, I see this l
Emmanuel Thomas-Maurin writes:
> I am looking for a sponsor for my package "i-news".
While I'm not a DD at the moment, so couldn't sponsor even if I wanted
to, but i-news - as already mentioned on -devel@ - is uncomfortably
similar to inews (which is a pure virtual package at the moment, but
sti
Emmanuel Thomas-Maurin writes:
> On 08/22/2011 11:29 AM, Gergely Nagy wrote:
>> While I'm not a DD at the moment, so couldn't sponsor even if I wanted
>> to, but i-news - as already mentioned on -devel@ - is uncomfortably
>> similar to inews (which is a pure vir
Gabriele writes:
> I'm having some hard times correcting these two errors
>
> E: pygtkplot: changelog-file-not-compressed changelog
> E: pygtkplot: manpage-not-compressed usr/share/man/man1/pygtkplot.1
>
> Must I compress the file by hand? If i compress the changelog then debuild
> says that it c
Hi!
A few comments and questions, if I may:
* Why is the package packaged as Debian native, when it is definitely
not Debian specific?
* Why does it have an ubuntu distribution in debian/changelog, and an
Ubuntu Section in debian/control, if it is meant to be uploaded to
Debian?
* Whe
Emmanuel Thomas-Maurin writes:
> On 08/22/2011 12:49 PM, Gergely Nagy wrote:
>> Emmanuel Thomas-Maurin writes:
>>
>>> On 08/22/2011 11:29 AM, Gergely Nagy wrote:
>>>> While I'm not a DD at the moment, so couldn't sponsor even if I wanted
>&g
Gabriele writes:
> I don't see the problem. I think I have already solved all those issues. In
> fact:
Hrm. I might have downloaded an earlier version then, I guess. Sorry for
the noise then!
On the other hand, I had a quick look at your updted 0.1-1 package, and
while it does look a thousand t
Emmanuel Thomas-Maurin writes:
> Dear mentors,
>
> Thank you for your answers. Well, until/unless I find a better
> alternative name, I will keep the current one at the moment.
What was wrong with 'tickr' ?
--
|8]
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a su
Emmanuel Thomas-Maurin writes:
> On 08/27/2011 10:29 AM, Gergely Nagy wrote:
>> Emmanuel Thomas-Maurin writes:
>>
>>> Dear mentors,
>>>
>>> Thank you for your answers. Well, until/unless I find a better
>>> alternative name, I will keep the cu
Hi!
The Q&A on mentors.d.n wasn't quite clear on whom I shall contact in
cases like this, but figured there's no harm asking on -mentors@ either:
Someone, somewhen uploaded a dpatch 2.0.31-1[1] package to mentors.d.n,
before it became debexpo. That version is well.. lets just say,
obsolete. Howev
Jeroen Schot writes:
> On Tue, Aug 30, 2011 at 01:07:28PM +0200, Sven Hoexter wrote:
>> On Tue, Aug 30, 2011 at 12:27:35PM +0200, Jeroen Schot wrote:
>> > I: cvsconnect source: debian-watch-file-is-missing
>> >
>> > This is because the upstream source is no longer available.
>>
>> Well then kil
Jeroen Schot writes:
> On Tue, Aug 30, 2011 at 07:56:16PM +0200, Gergely Nagy wrote:
>> Jeroen Schot writes:
>> > On Tue, Aug 30, 2011 at 01:07:28PM +0200, Sven Hoexter wrote:
>> I'd mention the CVS repo in debian/copyright. A dead link, however
>> historical
Marc Haber writes:
> On Tue, Sep 13, 2011 at 04:17:12PM +0200, Innocent De Marchi wrote:
>> I am looking for a sponsor for my package "gentoo".
>>
>> * Package name: gentoo
>>Version : 0.19.11-1
>>Upstream Author : Emil Brink
>> * URL : http://www.obsession.se/
Jose Ernesto Davila Pantoja writes:
> I am looking for a sponsor for my package "glipper".
>
> * Package name: glipper
> Version : 2.1-1
> Upstream Author : Laszlo Pandy
> * URL : https://edge.launchpad.net/glipper
> * License : GNU GPL v2
> Section
(Note: I didn't have a look at either package; I merely read the
preceding discussion in the bug log)
>From what I've read so far, my impression is that this is not a
technical issue, but more a social / team-work... misunderstanding,
perhaps.
So read my comments below, with these things in mind.
I wanted to comment on this thread, but for some reason, it always fell
off my radar. No more!
Ansgar Burchardt writes:
> I do not sponsor very much,
While I don't sponsor at all at the moment, because I'm not a DD right
now, if and when I become one, I do wish to sponsor from time to
time. And
Ansgar Burchardt writes:
> Gergely Nagy writes:
>> Ansgar Burchardt writes:
>>> - mentors.d.n automatically closes RFS bugs for uploaded packages or
>>>packages that were removed from there. It may also automatically
>>>close inactive bugs.
&g
Ansgar Burchardt writes:
>>> - pending (closing the bug): Somebody will (did) upload the package
>>> (no further changes required).
>>
>> I'm not sure if "pending" would be ever useful (except maybe for
>> uploads to DELAYED).
>
> Hmm, I thought about using it in case the sponsor did review the
Gergely Nagy writes:
> Wouldn't the "fixed" tag work for cases where the package is reviewed,
> and will be uploaded VerySoon(tm)?
Please disregard that, I had a brainfart. Apologies for the noise.
--
|8]
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.
Stefan Ott writes:
> Alternatively, one can download the package with dget using this command:
>
> dget -x
> http://mentors.debian.net/debian/pool/main/p/pidgin-privacy-please/pidgin-privacy-please_0.7.1-1.dsc
>
> I would be glad if someone uploaded this package for me.
I noticed two things w
Ole Streicher writes:
>> If it has a contrib/non-free build-dependency, the source package needs
>> to go to contrib as well. It cannot build binaries in main in that
>> case.
>
> My problem here is: the source package contains libwcs which may be
> built (and used) completely without non-free d
Antonio Ospite writes:
> I packaged kboot-utils (Helper tools to generate a kboot.conf file) for
> debian, and I'd like to ask if someone can *review* the package and
> maybe eventually sponsor me for upload to the main archive.
While I can't sponsor you, I did have a quick glance over the pack
Tristan Lelong writes:
> There is a dedicated webpage with online doxygen documentation:
> http://www.libroxml.net
> Debian packages (.deb / .orig.tar.gz / .diff.gz / .dsc / .changes) for
> current version (2.1.1) can be found at: http://debian.libroxml.net
In the future, could you provide a dir
Hi!
As promised, a couple of notes regarding the packaging:
* Is there any particular reason you're not using 3.0 (quilt) source
format?
Not a bug, just curious.
* debian/README & debian/control
Most of the content is better suited for the long description. When
the package is already
Eshat Cakar writes:
> You can see it in action, in this video
> http://youtu.be/aLtIvEiDD2k?t=2m1s
Great video, cheers!
> I would be glad if someone uploaded this package for me.
While I can't help you with uploading, I glanced over the packaging, and
would like to comment on a few bits and pi
1 - 100 of 266 matches
Mail list logo
