Package: wnpp
Severity: wishlist
Owner: "Gudjon I. Gudjonsson"
* Package name: liborigin2
Version : 20081216
Upstream Author : Stefan Gerlach
* URL : http://liborigin.sourceforge.net/
* License : GPL-2
Programming Lang: C
Description : library for read
On Sat, Mar 07, 2009 at 12:53:10AM +, Per Andersson wrote:
> On Fri, Mar 6, 2009 at 5:46 PM, Debian Project Secretary
> wrote:
> > To be valid, a Debian Developer needs to send a signed email in
> > which he nominates himself to the debian-v...@lists.debian.org
> > list.
> Can't women nominat
On Fri, Mar 6, 2009 at 5:46 PM, Debian Project Secretary
wrote:
> To be valid, a Debian Developer needs to send a signed email in
> which he nominates himself to the debian-v...@lists.debian.org
> list.
Can't women nominate themselves?
Best regards,
Per
--
To UNSUBSCRIBE, email to debian-dev
Andreas Tille, le Fri 06 Mar 2009 10:09:36 +0100, a écrit :
> On Thu, 5 Mar 2009, Samuel Thibault wrote:
> >> $ apt-cache search accessibility
> >>
> >>which is quite weak.
> >
> >Tags FTW. Look for Accessibility tags and you'll find a lot of
> >packages.
>
> Sure. But do all our package handl
On Sat, Mar 7, 2009 at 12:10 AM, Sandro Tosi wrote:
> On Fri, Mar 6, 2009 at 23:44, Mikael Djurfeldt wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Mikael Djurfeldt
>>
>> * Package name : music
>> Version : 1.0.1
>> Upstream Author : Name
>> * URL : http://soft
Package: wnpp
Severity: wishlist
Owner: Mikael Djurfeldt
* Package name: music-bin
Version : 1.0.1
Upstream Author : Name
* URL : http://software.incf.org/software/music/home
* License : GPL
Programming Lang: C++
Description : Multi-Simulation Coordin
Package: wnpp
Severity: wishlist
Owner: Mikael Djurfeldt
* Package name: music-doc
Version : 1.0.1
Upstream Author : Name
* URL : http://software.incf.org/software/music/home
* License : GPL
Programming Lang: C++
Description : Multi-Simulation Coordin
Package: wnpp
Severity: wishlist
Owner: Mikael Djurfeldt
* Package name: libmusic-dev
Version : 1.0.1
Upstream Author : Name
* URL : http://software.incf.org/software/music/home
* License : GPL
Programming Lang: C++
Description : Multi-Simulation Coor
Package: wnpp
Severity: wishlist
Owner: Mikael Djurfeldt
* Package name: libmusic1
Version : 1.0.1
Upstream Author : Name
* URL : http://software.incf.org/software/music/home
* License : GPL
Programming Lang: C++
Description : Multi-Simulation Coordin
On Fri, Mar 6, 2009 at 23:44, Mikael Djurfeldt wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Mikael Djurfeldt
>
>
> * Package name : music
> Version : 1.0.1
> Upstream Author : Name
> * URL : http://software.incf.org/software/music/home
> * License : GPL
>
Package: wnpp
Severity: wishlist
Owner: Mikael Djurfeldt
* Package name: music
Version : 1.0.1
Upstream Author : Name
* URL : http://software.incf.org/software/music/home
* License : GPL
Programming Lang: C++
Description : ITP: music -- Multi-Simulati
Package: wnpp
Severity: wishlist
Owner: Mikhail Gusarov
* Package name: inosync
Version : 0.2
Upstream Author : Benedikt Böhm
* URL : http://bb.xnull.de/projects/inosync/
* License : BSD3
Programming Lang: Python
Description : Notification-based direc
user pkg-fso-ma...@lists.alioth.debian.org
usertags 518494 + package-creation
thanks
Hi Yaroslav!
Please keep the pkg-fso-maint mailing list cc:ed, TIA.
On Fri, 06 Mar 2009 16:25:16 +0100, Yaroslav Halchenko wrote:
> * Package name: pythm
> Version : 0.5.5-dmr (fork developed by Dy
Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko
* Package name: pythm
Version : 0.5.5-dmr (fork developed by Dylan)
Upstream Author : Matthias Hans , Dylan Reilly
, and others ;)
* URL : http://github.com/negi/pythm/tree/master
* License : GPL-2+
On Fri, 06 Mar 2009, Michael Biebl wrote:
> I think the wiki page you mentioned with up-to-date information regarding this
> topic would really be a good idea.
Yeah, I've noted that and will set it up.
> >> Build-Depends, it would imho be useful if lintian issued a warning, that
> >> this
> >>
Хотите ручки с вашим лого? Звоните!
0442270304
Raphael Hertzog wrote:
> On Fri, 06 Mar 2009, Michael Biebl wrote:
>> dpkg-gencontrol: warning: unknown information field 'Format' in input data in
>> general section of control info file
>>
>> Should I file a bug against dpkg-dev for that?
>>
>> And another minor issue: vim doesn't know about the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Fr den 6. Mär 2009 um 14:19 schrieb Arthur de Jong:
> FWIW, I have a similar setup and cannot reproduce this:
Strange. It was just a suggestion. Lets look further to find the Bug.
> # uname -a
> Linux bobo 2.6.26-1-amd64 #1 SMP Sat Jan 10
On Thu, 2009-03-05 at 09:58 +0100, Klaus Ethgen wrote:
> Well, I did also some tests and wasn't able to trigger that bug on my
> laptop too. But I also have the lvm direct on the hard disk. On my
> server there is a md device underlying. So I suggest the problem is
> just with a lvm on top of a md
Package: wnpp
Severity: wishlist
Owner: "Sébastien Villemot"
* Package name: dynare
Version : 4.0.3
Upstream Author : Michel Juillard
* URL : http://www.dynare.org/
* License : GPL v3 for the program, GFDL v1.3 for the documentation
Programming Lang: C++, G
On Fri, Mar 06, 2009 at 09:07:58PM +1100, Ben Finney wrote:
> Thank you for your patient explanations of the underlying
> issues.
It's threads like these which restore my faith in humanity,
or the subset of humanity represented by -devel at least.
--
Jon Dowland
--
To UNSUBSCRIBE, email to d
Raphael Hertzog writes:
> On Fri, 06 Mar 2009, Ben Finney wrote:
> > Yes, that could be done. It needs to be done by every user, for
> > every patch that they ever create for consumption with
> > ‘dpkg-source’. Which is why I was hoping for a way to fix it in
> > one place, for ‘dpkg-source’ spec
Package: wnpp
Severity: wishlist
Owner: Daniel Watkins
* Package name: python-django-contact-form
Version : 0+hg61
Upstream Author : James Bennett
* URL :
http://bitbucket.org/ubernostrum/django-contact-form/overview/
* License : BSD
Programming Lang: Pytho
On Fri, Mar 06, 2009 at 07:48:27PM +1100, Ben Finney wrote:
> More specifically, I'm not the one using Quilt *at all*. The patches
> are created from my VCS, stored in the ‘debian/patches/’ directory
> separate from the upstream source, so there isn't anything for them to
> be applied to until the
On Fri, 06 Mar 2009, Ben Finney wrote:
> Raphael Hertzog writes:
>
> > On Fri, 06 Mar 2009, Ben Finney wrote:
> > > More specifically, I'm not the one using Quilt *at all*. The patches
> > > are created from my VCS, stored in the ‘debian/patches/’ directory
> > > separate from the upstream source
Raphael Hertzog writes:
> On Fri, 06 Mar 2009, Ben Finney wrote:
> > More specifically, I'm not the one using Quilt *at all*. The patches
> > are created from my VCS, stored in the ‘debian/patches/’ directory
> > separate from the upstream source, so there isn't anything for them to
> > be applie
On Thu, 5 Mar 2009, Samuel Thibault wrote:
$ apt-cache search accessibility
which is quite weak.
Tags FTW. Look for Accessibility tags and you'll find a lot of
packages.
Sure. But do all our package handling tool support DebTags?
Are our users aware of DebTags. (Well I admit they migh
On Fri, 06 Mar 2009, Ben Finney wrote:
> More specifically, I'm not the one using Quilt *at all*. The patches
> are created from my VCS, stored in the ‘debian/patches/’ directory
> separate from the upstream source, so there isn't anything for them to
> be applied to until the package gets built wi
Ben Finney writes:
> Raphael Hertzog writes:
>
> > Quilt make it easy to refresh any patch to the expected format
> > with "quilt refresh -p1" (or -pab).
>
> I'm a complete neophyte at Quilt, and am using it only to apply
> patches that I've already created elsewhere. Can I expect ‘quilt
> ref
On Fri, 06 Mar 2009, Ben Finney wrote:
> > Furthermore, I believe that consistency is important and that we're
> > better with all patches formatted in the same way. Quilt make it
> > easy to refresh any patch to the expected format with "quilt refresh
> > -p1" (or -pab).
>
> I'm a complete neophy
On Fri, 06 Mar 2009, Lucas Nussbaum wrote:
> > Did you also test if they produce the same content?
>
> Many packages don't produce the same content after each build, because
> of timestamps written in some files, for example. I could easily check
> that they provide the same binary packages accord
On Thu, 05 Mar 2009, Luk Claes wrote:
> > as announced earlier during the lenny dev cycle, I would like to switch to
> > the new source package formats ("3.0 (quilt)" and "3.0 (native)") during
> > the squeeze cycle so that we can benefit from the numerous improvements.
> > For this kind of importa
On 05/03/09 at 22:35 +0100, Luk Claes wrote:
> > My goal is not only to accept them on ftp-master but also to update
> > dpkg-source to build new source package automatically. That's why I
> > rebuilt the archives to see what packages would not build with the
> > new format (without fixes). The fai
Raphael Hertzog writes:
> Supporting multiple -pX would increase the complexity of the
> associated code in a manner that is mostly incompatible with the
> various checks that have always been built into dpkg-source (and
> that were only applied on .diff). It's enough error-prone to mimick
> the
On Fri, 06 Mar 2009, Ben Finney wrote:
> > Note however that while dpkg-source parses correctly series files
> > with explicit options used for patch application (stored on each
> > line after the patch filename and one or more spaces), it does
> > ignore those options and always expect patches tha
35 matches
Mail list logo
