Hi,
I am currently working on my rkhunter package to improve the way its
database is updated on package upgrade/install/removal.
The aim is to only update file properties of the changed packages.
To achieve this goal, I need to get the list of changed packages, which
I do in a script invokef thr
Hello,
this RFS including following 7 source packages, which provide a
handwriting recognition input method for SCIM (now it can works for
Japanese and Simplified Chinese)
zinnia: ITP#514969, online handwriting recognition system with machine learning
tagaki: ITP#514973, core python module of Teg
2009/2/12 Miguel Landaeta :
>
> I am looking for a sponsor for my package "jabberd14".
>
I am looking at it.
By the way, could you upload your GPG key to a public server?
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1
2009/2/15 Miguel Landaeta :
> On Mon, Feb 16, 2009 at 12:02 PM, Jens Peter Secher wrote:
>>
>> By the way, could you upload your GPG key to a public server?
>
> Ok, my GPG key is already uploaded to subkeys.pgp.net.
Hmm, the only key there matching your name is 5305CDD0. The key which
signed the
Hi,
On Fri, Feb 13, 2009 at 10:39 PM, Daniel Baumann wrote:
> Raphael Geissert wrote:
>> http://mentors.debian.net/debian/pool/main/x/xinha/xinha_0.95-1.dsc
>
> sorry for the late answer. if still wanted, i can do a review beginning
> of next week.
Another review would help as it is a complex p
On Fri, 2009-02-13 at 16:54 +, Neil Williams wrote:
> > > I wonder what's the best workflow to adapt a patch to a changed
> > > source.
> > > [...]
> > > Even finding out the cause of the failure by examining the .rej file
> > > has
> > > been no success.
>
> You have to know what the chan
On Sun, Feb 15, 2009 at 08:55:33PM +0100, Andreas Schildbach wrote:
>
> dpatch-edit-patch does not allow editing a corrupt patch. Unfortunately,
> dpatch-edit-patch is the only way I know how to create a dpatch patch
> (besides writing it by hand).
A dpatch patch is just a normal patch file (with
On Sun, 2009-02-15 at 19:59 +, Jonathan Wiltshire wrote:
> > dpatch-edit-patch does not allow editing a corrupt patch. Unfortunately,
> > dpatch-edit-patch is the only way I know how to create a dpatch patch
> > (besides writing it by hand).
>
> A dpatch patch is just a normal patch file (wit
On Sun, Feb 15, 2009 at 09:04:19PM +0100, Andreas Schildbach wrote:
> So am I really supposed to create that patch file by hand in this case?
If you can reconstruct the patched source, then:
- apply the patch series as far as possible
- take a copy of this original source, and on the copy reconst
Hi
I do have a problem with the debian packaging tools but I don't know how
to debug it.
When I build one of my packages using
dpkg-buildpackage or ./debian/rules binary
the library files are installed into
debian/tmp/usr/lib/tcltk/spice
But if I use pdebuild, the same files are instal
2009/2/15 Gudjon I. Gudjonsson :
> How can there possibly be this difference between these two tools?
I don't know what could trigger something like this, but it may be
worth checking that you have the same build dependencies (and version
of them) installed as pbuilder gets.
--
Siegfried-Angel G
On Sun, 2009-02-15 at 20:07 +, Jonathan Wiltshire wrote:
> > So am I really supposed to create that patch file by hand in this case?
>
> If you can reconstruct the patched source, then:
>
> - apply the patch series as far as possible
The patch in question is the first in the series. Maybe l
Am Sonntag, den 15.02.2009, 20:47 +0100 schrieb Gudjon I. Gudjonsson:
> Hi
> I do have a problem with the debian packaging tools but I don't know how
> to debug it.
>When I build one of my packages using
> dpkg-buildpackage or ./debian/rules binary
> the library files are installed into
Hi Andreas,
On Sunday 15 February 2009 21:34:47 Andreas Schildbach wrote:
> This is the problem. dpatch-edit-patch does not let me do anything as
> long as the out-of-sync patch is in place.
>
> (01_build_xml is the out-of-sync patch, 01_build_xml_2 is the new patch
> I want to create as a replace
On Sun, Feb 15, 2009 at 09:34:47PM +0100, Andreas Schildbach wrote:
> This is the problem. dpatch-edit-patch does not let me do anything as
> long as the out-of-sync patch is in place.
So take it out of place. A dpatch is two things: the patch file, and its
entry in debian/patches/00list. Take its
2009/2/12 Miguel Landaeta :
>
> I am looking for a sponsor for my package "jabberd14".
>
The package looks good, except for a few things:
- The Depends for libjabberd2-dev should be
libjabberd2 (= ${binary:Version}).
- /var/spool/jabberd (and old /var/lib/jabber) is not deleted on
purge. Sh
Paul Wise wrote:
> On Fri, Feb 13, 2009 at 9:59 PM, ERSEK Laszlo wrote:
>
>> Citing the "Version", "File size [B]" and "Decompr. speed [%]" blocks from
>> "report_alpha_osf1.txt" (I mark the relevant rows with exlamation marks
>> now):
>
> Ok, these numbers convinced me lbzip2 is better.
... fo
Hi Julien,
Julien Valroff wrote:
> The aim is to only update file properties of the changed packages.
>
> To achieve this goal, I need to get the list of changed packages, which
> I do in a script invokef through Pre-Install-Pkgs.
>
> The file properties can however only be updated once the packa
Paul Wise wrote:
> And now onto the package review:
>
> Why does your diff.gz patch the Makefile? Shouldn't you add those
> changes to the upstream Makefile?
I don't think so. As my general, hobbyist free software development
policy, I *always* and *exclusively* follow the Single Unix Specificat
Dear mentors,
I am looking for a sponsor for the new version 0.5-1 of package "cgmail" that I
would like to adopt.
It builds these binary packages:
cgmail - A new shiny mail checker for the GNOME desktop
The package appears to be lintian clean. (Depending on what you call clean ;-))
$ lint
Le dimanche 15 février 2009 à 21:15 +, Jörg Sommer a écrit :
> Hi Julien,
Hi Jörg,
> Julien Valroff wrote:
> > The aim is to only update file properties of the changed packages.
> >
> > To achieve this goal, I need to get the list of changed packages, which
> > I do in a script invokef throu
On Mon, Feb 16, 2009 at 04:20, wrote:
> My alioth id is xnox-guest and I would like to join and maintain this
> package under Python
> Apps Team in their SVN. (Although I don't know how to use SVN, git was first
> and later I
> learned bzr).
you'd be welcome to so do :) You can find some documen
22 matches
Mail list logo
