On Tue, Jun 10, 2008 at 12:07 PM, Gonéri Le Bouder <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 10, 2008 at 04:54:36PM +1000, Jack Coulter wrote:
>> Dear mentors,
>
> Hi Jack,
>
> some remarks.
> debian/control:
> -You should remove the -dbg packages from the build dependency.
>
> debian/rules:
> -it's
On Fri, Jun 13, 2008 at 4:51 PM, Pietro Battiston <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> After writing this, I found a wonderful FAQ saying I should add
> informations to make the package interesting, so I'm answering to myself.
>
> Pietro Battiston ha scri
Dear mentors,
I am looking for a sponsor for my package "sympy".
* Package name: sympy
Version : 0.3-1
Upstream Author : Ondrej Certik <[EMAIL PROTECTED]>
* URL : http://code.google.com/p/sympy/
* License : GPL
Section : python
It bui
elieve that
fixing the previous point will just fix this one automatically
* the debian/rules contains some unnecessary things, but I just left
it there until we fix the above problems
* also please check that I removed all the non-free things correctly
Kind regards
Ondrej Certik
--
To UNSUBS
Hi Alan,
thanks for looking at that. Here is the new dsc:
http://mentors.debian.net/debian/pool/main/l/libmesh/libmesh_0.6.0~rc2.dfsg-1.dsc
The package is now lintian&linda clean, builds fine in pbuilder.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426734 seems to have
appeared now.
Fi
nice, if it was in Debian, even though as non-free.
Kind regards
Ondrej Certik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
If the upstream tarball contains non-free sources, you'll have to
repackage it. See section 6.7.8.2 of the developers' reference[1].
Naturally, it must also /work/ without the parts you've removed. If
possible and useful, you may want to consider moving the parts that
have been removed to packages
alculation in Debian. Similar ones, but much larger are:
http://www.abinit.org/
http://exciting.sourceforge.net/
But those packages are written in fortran, but openmx is written in C,
that's why I prefer it.
Kind regards
Ondrej Certik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
If you are not already aware of it, there is discussion on debian-vote
about "Debian Maintainers" - "letting people maintain
specific packages in the archive without being full developers".
I thought I would mention it here as non-DDs are not too likely to read
d-vote, but might be greatly affect
I am looking for a sponsor for the new version 2.0rc2-1.1
of my package "pytables".
It builds these binary packages:
python-tables - hierarchical database for Python based on HDF5
python-tables-doc - hierarchical database for Python based on HDF5 -
documentation
The package appears to be lintia
There is also another point that I think wasn't yet mentioned - I, as
a non DD, create packages mainly because I myself want them, because
it is very comfortable. However, with a new package, it takes usually
a month or two, until it hits the unstable (many days to find a
sponsor and fix all small
Ondrej, Charlie,
You can also ask for sponsor for -2, even while -1 is in NEW. This won't
"disturb" the package for sure. The first version in unstable would
simply be -2. For example, see console-setup having two versions in NEW[1].
[1] http://ftp-master.debian.org/new.html
This feature is esp
> I also vaguely recall some actions which work as an ordinary
> user but fail under fakeroot; due to a difference in behaviour. I no
> longer can recall the details, though, so I could be mistaken.
The bzr test suite, for one.
Or libslepc2.3.2 configure refuses to configure tha pack
The actual discussion came up when we talked about whether the current
GR on non-DDs with upload permissions is good or bad for Debian. And we
agreed that Debian lacks a lot of packages just because the poor package
maintainer (tm) didn't find a sponsor in time.
Yes, that is the most difficult p
I find it easy enough to do:
$ sudo apt-get update
$ apt-src -bi install $package
apt-src will then "install" the source of the package into the current
working directory, then "b"uild it, and then "i"nstall the resulting
binaries.
Thanks for the tip. This is actually very comfortable and wor
> I find it easy enough to do:
>
> $ sudo apt-get update
> $ apt-src -bi install $package
>
> apt-src will then "install" the source of the package into the current
> working directory, then "b"uild it, and then "i"nstall the resulting
> binaries.
>
> This works just fine for me with the deb-src me
> Do you know why it does that? I'm curious about exactly what
> fails. mailagent, for example, has checks to see if some files are
> (correctly) unreadable, which would fail if the check was run as
> root. I actually check to see if the check is being run as root, and,
> if so, su to
Hi,
I often have problems installing Debian using the official installer,
the kernel is too old, so that it either doesn't boot or some drivers
(like ethernet card or cdrom) aren't working -- happens to me always
when installing on a new computer, once two years ago, twice a year
ago and once toda
> So I try to install by hand using debootstrap, usually from Knoppix,
> if possible. Unforunately, it usually doesn't load on new computers
> either.
BTW, today, the debootstrap won't even build the base system without
problems (it even tries to install x11-common !). I use pbuilder, that
fortuna
Hi,
I would like to create something like the Ubuntu Personal Package
Archive (PPA), but for Debian. It should be a single package, which
one just installs and it just woks. My current code is here:
http://code.google.com/p/debppa/
It's written in Django (Python) and my idea is to have a simple
> > So I'll install the "debppa" packge (ideally using one command)
>
> apt-get install debppa?
Exactly like this when I get it to Debian. Ideally, there shouldn't be
any other setup, one would just start a command, let's say debppa, or
/etc/init.d/debppa start, and could immedatelly use it on the
> Thanks for sharing. Do you know the debian-live project?
No, I didn't, thanks for the info. I put that into the links.
> Your CD scripts were interesting since they're very compact (~130
> lines) whereas d-l is much larger (~11k lines).
It's actually only 86 lines, the relevant files are thes
> Many Debian packages aren't designed to support cross-compilation.
> Currently the only way to reliably build for multiple architectures is
> to build on multiple architectures.
I just found a "qemubuilder" packages, from the same author as
pbuilder and cowbuilder and can build packages for diff
> Thank you very much for reading until here! Any comments (also on different
> topics) are very much welcome!
Thank you for doing the packaging! I didn't know about the program
before, I just tried your .deb and it looks very good (both the
packaging and gwyddion). I am looking forward when you r
> > Metrology institutes define the measurement standards so
> > that you can compare the lengths of metrology and
> > meteorology and find that the latter is 22.2% longer...
> shame on me, that I missed these 22.2%...
> I shouldn't be trying to read and write mail in the evening with a heada
Hi Sam,
> pyxplot - Command-line plotting package producing publication-quality output
>
> Chances in this version:
> * Repack upstream tarball to remove contained PyX tarball and HTML
> documentation.
> + 200_build-docs-verbose.patch: don't try to unpack PyX's tarball and
> instal
> > * the package looks good, it is lintian/linda clean and builds in cowbuilder
> > * Why not to join the PAPT team and let it maintain as part of it?
> >
> > http://wiki.debian.org/Teams/PythonAppsPackagingTeam
>
> Sounds nice, but I want to keep using git rather than subversion. :(
Right. I thi
Hi,
I am using cowbuilder for building my packages, because the
initialization takes like 10s, compared to several minutes with
pbuilder on my system. A few days ago, I realized that on one of my
systems, it takes 0.5s only to copy the COW directory. I became
curious and wanted to know why, so I d
> Does this possibly have to do with buffer flushing choices by the
> filesystem? Maybe xfs syncs after some operations (like rm -rf) that ext3
Probably not.
> does not.
>
> Try adding 'sync' after both steps and see if that changes performance.
I did, see "Note 3" in the wiki. It's actually XF
> > Try adding 'sync' after both steps and see if that changes performance.
>
> I did, see "Note 3" in the wiki. It's actually XFS, that caches things
> on amd64, so with sync, the XFS takes 3.5s on amd64 (instead of those
> 0.5s). But ext3 with sync is still very fast (from 0.2s to 0.4s)
> everywh
> > it turned out the problem is in the XFS filesystem, that is 20x slower,
> > than the ext3 filesystem. I know that XFS is bad at handling small
> > files, but 20x times?
>
> Try to play with parameters mentioned in laptop-mode.txt in the Linux
> sources.
>
> Then, try to have XFS log area on sep
> Dear mentors,
>
> I am looking for a sponsor for my package "nted".
>
> * Package name: nted
>Version : 0.6.2-1
>Upstream Author : Jörg Anders <[EMAIL PROTECTED]>
> * URL :
> http://vsr.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html
> * License : GPL
> NtEd requires the ALSA sequencer device (/dev/snd/seq). Just load the
> snd_seq module (modprobe snd_seq) and NtEd shouldn't complain anymore.
It starts and it's a nice program, thanks. I use lilypond though,
together with lilicomp, but this is also nice. Taking into account
that nted cannot pla
> > It starts and it's a nice program, thanks. I use lilypond though,
> > together with lilicomp, but this is also nice. Taking into account
> > that nted cannot play on my computer by default (see below), I think
> > it should start even without "modprobe snd_seq". I think programs
> > should work
Hi,
> The sources:
> http://svn.debian.org/wsvn/collab-qa/svnbuildstat/?rev=0&sc=0
> The wiki page:
> http://wiki.debian.org/svnbuildstat
I believe Debian needs the same as Ubuntu has: Personal Package
Archives, where new maintainers could upload their source packages and
the service will automat
> It could be better. I just doubt that the "private" issue is the
> problem. Everybody who likes to get involved could always join the team.
> We are open. So it's really no giant master plan that the sources
> weren't made public yet. Perhaps with the relaunch we can start to make
I think it is
> Did Ondrej say that we need a public buildd? Actually that is something
> I would ratner not do because I have certain (very bad) experience with
> it. When we kept the uploaded binary (.deb) packages our support mailbox
> was literally flooded with end-users (!) complaints that the packages
> we
> times, but when I found some of the people here so nice and helpful, I
> could learn so much. The learning curve is quite long, and I still have
> so many things to learn.
>
> That vote system goes totally on the opposite direction, and
> blacklisting or discouraging people that are trying to lea
> > > I'm scared by the thought that there will be a dozen PPAs that end-users
> > > will use to get their software from third-party sources. IMHO good
> > > packages should go officially into Debian. And bad packages should go to
> > > hell. Sponsorship might be a problem sometimes which may be so
> > So at least I expect to come up with a Python module
> > that helps dealing with Debian source packages and repositories. I hoped
> > that python-apt would help but last time I looked it was only there to
> > deal with the APT cache. I spent a lot of time parsing control files
> > correctly and
> * Package name: ustr
> Version : 1.0.1-1
> Upstream Author : James Antill <[EMAIL PROTECTED]>
> * URL : http://www.and.org/ustr/
> * License : LGPL, BSD, MIT
> Section : libs
>
> It builds these binary packages:
> libustr-1.0-1 - Micro string library:
On 10/29/07, Thomas Goirand <[EMAIL PROTECTED]> wrote:
> Ondrej Certik wrote:
> >> Perhaps even for PPA-like services.
> >> I'm thinking a similar way (using a Python web framework - although a
> >> different one).
> >
> > Yeah, unforutun
On 10/29/07, Felipe Sateler <[EMAIL PROTECTED]> wrote:
> It might be interesting to have an additional "seeking comments" tag.
> Sometimes the package is not really ready for sponsorship, or the usual
> sponsor is too busy right now, and all I really care is for comments on the
> package rather tha
> > > Really, it may have sounded more rude to you, then it was meant to be.
>
> > > But I was really annoyed by such a statement,
> >
> > That rather implies you were unfriendly, at least I'm often (too)
> > unfriendly,
>
> Misusing "then" an
Hi Christoph!
On Mon, Nov 30, 2009 at 12:57 PM, Christoph Haas wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear list,
>
> I've been running mentors.debian.net for quite some years now. The
> software running the repository including importers, user handling,
> package checks and
On Mon, Dec 14, 2009 at 2:03 PM, Christoph Haas wrote:
> Hi, Ondrej…
>
> Ondrej Certik schrieb:
>> On Mon, Nov 30, 2009 at 12:57 PM, Christoph Haas wrote:
>>> I've been running mentors.debian.net for quite some years now. The
>>> software running the reposit
46 matches
Mail list logo
