On Thu, 2007-03-15 at 06:45 +0100, Christian Perrier said:
> Apart from "has anyone already done the same thing for the poor users
> of stone age VCS like Subversion"?
>
> During translation handling of several packages, I happen to commit a
> big bunch of updates, each supposed to fix a l10n bug
> Feedback appreciated.
Apart from "has anyone already done the same thing for the poor users
of stone age VCS like Subversion"?
During translation handling of several packages, I happen to commit a
big bunch of updates, each supposed to fix a l10n bug report and
sending a "Committed" mails with
Package: wnpp
Severity: wishlist
Owner: Dario Minnucci <[EMAIL PROTECTED]>
* Package name: svnmerge
Version : 20070315
Upstream Author : Amir Guindehi <[EMAIL PROTECTED]>
* URL : https://open.datacore.ch/DCwiki.open/Wiki.jsp?page=SVNmerge
* License : GPL (In con
Package: wnpp
Severity: wishlist
Owner: Dario Minnucci <[EMAIL PROTECTED]>
* Package name: svnreplicate
Version : 20070315
Upstream Author : Amir Guindehi <[EMAIL PROTECTED]>
* URL :
https://open.datacore.ch/DCwiki.open/Wiki.jsp?page=SVNreplicate
* License : GP
On Tuesday 13 March 2007 20.23:16 Roman Müllenschläder wrote:
> Because my laptop, where I'm building the packages on, is running Edgy ;)
>
> Maybe I should compile lintian by hand ... tried using sources from
> feisty but they need to much dependencies ...
If you're building packages for Debian,
Package: wnpp
Severity: wishlist
Owner: Dario Minnucci <[EMAIL PROTECTED]>
* Package name: svnbackup
Version : 20070315
Upstream Author : Amir Guindehi <[EMAIL PROTECTED]>
* URL : https://open.datacore.ch/DCwiki.open/Wiki.jsp?page=SVNbackup
* License : GPL (In c
Your message dated Wed, 14 Mar 2007 13:11:06 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#414937: Acknowledgement (general: network connection
issues, 90% connect
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt w
On Wed, Mar 14, 2007 at 08:26:36PM +0100, martin f krafft wrote:
> I am trying to package lightblue.sf.net, which does the following
> during installation:
>
> piper:.> python ./setup.py install --prefix=debian/python-lightblue/usr
> --no-compile
> running install
> running build
> runnin
Hi,
I thought some of you may be aware that I have developed some commit
hooks for Darcs and Mercurial. These hooks look for special strings in
your commit logs. You can give a string to notify the bug of the
commit, or another to do that plus mark the bug pending. These hooks
are based on trac
[martin f krafft, 14.03.2007]
> As you can see, it installs compiled .so files, making the package
> dependent on the python ABI, 2.4 in this case.
>
> How am I to deal with packages like this?
Make sure that you build .so for all supported python versions
(`pyversions -s`) and let py{support,cen
I am trying to package lightblue.sf.net, which does the following
during installation:
piper:.> python ./setup.py install --prefix=debian/python-lightblue/usr
--no-compile
running install
running build
running build_py
running build_ext
running install_lib
creating debian/python-lig
On Wed, Mar 14, 2007 at 12:28:31PM -0600, Gunnar Wolf wrote:
> > Why is every question I'm asking here treated like me beeing a child in
> > time,
> > not able to do the logical?
> >
> > Testing a package is useless and senseless ... I know that well!
>
> HUH!?!?
>
> Ummmh... If that's how you
Roman Müllenschläder dijo [Wed, Mar 14, 2007 at 12:16:31AM +0100]:
> > If you're developing packages for Debian, not Ubuntu, I would
> > suggest at a minimum that you do your builds in a Sid chroot
> > (pbuilder and/or UML work well for this too, depending on how
> > powerful your system is). I do
Roman Müllenschläder dijo [Tue, Mar 13, 2007 at 08:43:56PM +0100]:
> > > > So, why are you using a version that's not the one in testing, nor the
> > > > one in stable?
> > >
> > > Because my laptop, where I'm building the packages on, is running Edgy ;)
> >
> > I know I'm stating the obvious here
Roman Müllenschläder dijo [Tue, Mar 13, 2007 at 08:23:16PM +0100]:
> > The versions for lintian (from packages.qa.debian.org) are:
> >
> > Stable: 1.23.8
> > Testing:1.23.28
> > Unstable: 1.23.28
> >
> > So, why are you using a version that's not the one in testing, nor the
> > one in stab
Package: wnpp
Severity: wishlist
Owner: Stefano Zacchiroli <[EMAIL PROTECTED]>
* Package name: python-axiom
Version : 0.5.0
Upstream Author : Divmod Inc.
* URL : http://www.divmod.org/trac/wiki/DivmodAxiom
* License : MIT License
Programming Lang: Python
Des
Package: wnpp
Severity: wishlist
Owner: Stefano Zacchiroli <[EMAIL PROTECTED]>
* Package name: epsilon
Version : 0.5.0
Upstream Author : Divmod Inc.
* URL : http://divmod.org/trac/wiki/DivmodEpsilon
* License : MIT License
Programming Lang: Python
Descriptio
Am Mittwoch, 14. März 2007 schrieb Rene Engelhard:
> Hi,
>
> Roman Müllenschläder wrote:
> > The problem is that the mentioned lintian warning was fixed in .27 .. so
> > if testing and unstable are using .28, there should be no problem with
> > just ignoring the warnings for now and see what my _te
On Wed, Mar 14, 2007 at 09:45:08AM +0100, Bernhard R. Link wrote:
> In my eyes no program at all should store caches in $HOME. There is
> $TMPDIR for that. Even small files can be a big problem, if you have
> several hundred users.
But if TMPDIR="$HOME/tmp" then you have the same problem. Further
On Wednesday 14 March 2007, Josselin Mouette wrote:
> Le mercredi 14 mars 2007 à 09:45 +0100, Bernhard R. Link a écrit :
> > Against those grotesque
> > .fonts.cache-1 files (which are not only cache that should not be in
> > /home, but also system dependent thus even more do not belong there)
> >
Le mercredi 14 mars 2007 à 09:45 +0100, Bernhard R. Link a écrit :
> Against those grotesque
> .fonts.cache-1 files (which are not only cache that should not be in
> /home, but also system dependent thus even more do not belong there)
> running fc-cache as root on all hosts regulary helps.
The sys
On Wed, Mar 14, 2007, Pierre THIERRY wrote:
> I just discovered today that some packages can store pretty huge cache
> data in my $HOME, and found that rather problematic. When I backup my
> home, I don't want to waste backup space or time to do it, because I
> have to check what eats space and te
On Wed, 14 Mar 2007, Bernhard R. Link wrote:
> * Pierre THIERRY <[EMAIL PROTECTED]> [070314 07:51]:
> > I just discovered today that some packages can store pretty huge cache
> > data in my $HOME, and found that rather problematic. When I backup my
> > home, I don't want to waste backup space or ti
* Pierre THIERRY <[EMAIL PROTECTED]> [070314 07:51]:
> I just discovered today that some packages can store pretty huge cache
> data in my $HOME, and found that rather problematic. When I backup my
> home, I don't want to waste backup space or time to do it, because I
> have to check what eats spac
Hi,
Roman Müllenschläder wrote:
> The problem is that the mentioned lintian warning was fixed in .27 .. so if
> testing and unstable are using .28, there should be no problem with just
> ignoring the warnings for now and see what my _tests_ on debian will
No, that's wrong. *Build* also on Debia
25 matches
Mail list logo
