-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 06 Sep 2017 20:30:22 +0300
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source amd64
Version: 1.14-1
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh <shac...@debian.org>
Changed-By: Shachar S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 27 Nov 2016 20:26:18 +0200
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source amd64
Version: 1.13-1
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh <shac...@debian.org>
Changed-By: Shachar S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Jul 2016 20:45:15 +0300
Source: argtable2
Binary: libargtable2-dev libargtable2-docs libargtable2-0
Architecture: source amd64 all
Version: 13-1
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh <s
I am working on bringing the libargtable2 package up to date with both
upstream changes and the Debian policy. One of the changes state:
recommend to ship additional documentation for package |pkg| in a
separate package |pkg-doc| and install it into |/usr/share/doc/pkg|.
The package currently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 02 Jul 2016 05:43:19 +
Source: sshpass
Binary: sshpass
Architecture: source amd64
Version: 1.06-1
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh <shac...@debian.org>
Changed-By: Shachar Shemesh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Jun 2016 08:48:31 +
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source amd64
Version: 1.12-2
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh <shac...@debian.org>
Changed-By: Shachar S
On 16/11/14 17:16, Scott Kitterman wrote:
The cure for inappropriate speech is more speech. Calling people on things
that are inappropriate or that cause problems in the project is exactly the
right thing to do.
I was trying to point out the futility of trying to ask people to show
On 13/11/14 18:22, Tobias Frost wrote:
Sometimes, a joke is just inappropriate, regardless how funny it may seem.
Sometimes, a joke is better not made, regardless how funny it is.
We have enough bad karma these days, no need to pour gasoline on the fires.
Civility ism after all, so important
Just a quick FYI for anyone who missed it.
Following the discussion from a few days ago about Cava (C like language
with no undefined behavior), gcc 4.9 is now out[1]. One of the changes
there is a runtime check for undefined behavior. Just compile with
-fsanitize=undefined, and your program will
On 15/04/14 19:45, Jakub Wilk wrote:
* Thorsten Glaser t...@mirbsd.de, 2014-04-15, 11:24:
we need to go further. We need a programming language (with at least
two compiler implementations), which I will call Ͻ, that looks like C
so much that *every* C program¹ is also a valid Ͻ program, and
On 13/04/14 06:32, Russ Allbery wrote:
Like I said before, I am not against the compilers warning about such
cases. I just think that these warnings need to be done very carefully,
or they become worse than useless. As such, if you see a case in which
you feel gcc (or clang, or whatever)
On 12/04/14 23:38, Henrique de Moraes Holschuh wrote:
On Thu, 10 Apr 2014, Shachar Shemesh wrote:
I never did understand what people expect. gcc uses the undefined
Warn the hell out of any line of code with per-spec undefined behaviour, if
not by default, at least under -Wall.
I have
On 13/04/14 05:39, Russ Allbery wrote:
One can make a good argument that such checks are exactly what you should
be doing.
Then the answer is very simple. Write in Java.
My understanding of things is that undefined behaviors are fairly
common, and almost always benign. Look at the following
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 12 Apr 2014 16:34:11 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source amd64
Version: 0.18-4
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh
On 11/04/14 13:49, Ansgar Burchardt wrote:
Hi,
On 04/11/2014 12:42, Ian Jackson wrote:
What people expect is that the compiler compiles programs the way C
was traditionally compiled.
Shouldn't -O0 come close to that expectation?
I think that Ansgar's answer is spot on, but against all good
On 10/04/14 20:59, Ian Jackson wrote:
Vincent Lefevre writes (Re: Having fun with the following C code (UB)):
On 2014-04-10 11:48:44 +, Thorsten Glaser wrote:
And GCC is a repeat offender which actually does do that.
If you don't like that, you should use the -fwrapv option.
Sadly that
On 26/03/14 17:13, Kevin Toppins wrote:
I am going to have to respectfully disagree with you on my post being useless.
With the hope of contributing constructive criticism, I'll answer that.
As far as the systemd vs. upstart discussion, I was leaning in upstart
(more precisely, against systemd).
On 23/01/14 13:45, Richard Hartmann wrote:
The risk of any outsider to become a DD for this offer alone is slim to
none.
You're forgetting the free LWN subscription.
Shachar
Hi all,
I have a package[1] that will not transition to testing due to failed
compilation on powerpc. The problem is that the actual package requires
a fairly complete C++11 support in order to compile. I have tried to
signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies.
On
Hi all,
I have a package[1] that will not transition to testing due to failed
compilation on powerpc. The problem is that the actual package requires
a fairly complete C++11 support in order to compile. I have tried to
signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies.
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 13 Apr 2013 08:09:46 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source amd64
Version: 0.18-3
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 12 Apr 2013 13:14:05 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source amd64
Version: 0.18-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 12 Apr 2013 17:26:11 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source amd64
Version: 0.18-2
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 06 Aug 2011 20:23:50 +0300
Source: sshpass
Binary: sshpass
Architecture: source amd64
Version: 1.05-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
(and other)
mailing lists as non-email forums.
But I believe that this is also something that can be resolved using
technical means. I think the current policy is unnecessarily complex if
followed, and in practice is not followed at all, leading to sub-optimal
behavior.
Shachar
--
Shachar Shemesh
achieved.
Also, reply-to is the wrong tool for this job (this is NOT what it's
for), as it prohibits distinction between replies to the list and reply
to me.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ
though
and you could also set Reply-To: to both the list and your address.
A. I'm not at all sure what the standard says about multiple Reply-To:
headers. I don't think they are supported
B. Even if they are, they still don't allow people to reply privately.
Shachar
--
Shachar Shemesh
Lingnu
the mailing
participants switched to mailman, and the result was quiet on the 'reply
to all' front for several years now.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject
round.
non-free stuff shouldn't be in main depends at all IMO, even as an alternative.
Then please state what you think should happen in the case pointed out
by Emilio.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email
On 23/02/11 12:23, Holger Levsen wrote:
Hi,
On Mittwoch, 23. Februar 2011, Shachar Shemesh wrote:
Giving feedback over the
upstream trustworthiness is not the purpose of ITP bugs,
oh, hell yes, it is.
Where else should we discuss what software fits into Debian? debian-qa@ when
it's
Package: wnpp
Severity: wishlist
Owner: Shachar Shemesh shac...@debian.org
* Package name: libsafewrite
Version : 1.00
Upstream Author : Shachar Shemesh shac...@lingnu.com
* URL : http://www.lingnu.com/opensource/safewrite.html
* License : MIT
Programming
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d648429.5010...@debian.org
against DESTDIR installed libraries (maybe make it
respect DESTDIR if it's defined during the build? That could be a
solution that is both easy to understand and simple to integrate)
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
for open, plus
safe_write.h itself. I don't see that as particularly burdensome. I'm
not sure how platform independent any includes I put inside my header
are going to be, and would rather not open this particular can of worms.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http
on
PATH_MAX is. I think the current implementation solves both of these
concerns.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
On 04/01/11 16:24, Ian Jackson wrote:
Shachar Shemesh writes (Safe file update library ready (sort of)):
This is not a formal release just yet (plus one function is still
missing an implementation, trivial though it might be). It's just that
the list obviously has a few people knowledgeable
this weekend. I
even gave a URL to watch (https://github.com/Shachar/safewrite). If you
check it out right now, you will find there a fully implemented and
fairly debugged user space solution, even including a build tool and man
page.
BTW - feedback welcome.
Shachar
--
Shachar Shemesh
Lingnu Open
appreciated.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d21a84c.4060...@debian.org
opening it with O_CREAT|O_TRUNC. The reason is that
it might have permissions (say, from a previous run that failed -
unlikely, but not impossible) that prevent proper functioning. It has
nothing to do with permissions.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http
On 03/01/11 14:54, Olaf van der Spek wrote:
That's one of the more interesting parts.
It sure is to you. I'm not sure about other users. I'll tell you what -
I'll make the project's home page a wiki, and you can document these to
your heart's content.
Shachar
--
Shachar Shemesh
Lingnu
to let anyone who disagrees with this statement
come forward and say so.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
opening it with O_CREAT|O_TRUNC. The reason is that
it might have permissions (say, from a previous run that failed -
unlikely, but not impossible) that prevent proper functioning. It has
nothing to do with permissions.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http
handle copying the permissions over and
following symlinks.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive
on any Posix). Pointers/patches once
released are, of course, welcome :-)
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
. Will also handle copying the permissions over and
following symlinks.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
file had (including owner, permissions etc.)
Just thought I'd share this little nugget to show you how much worse
non-posix has it.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
. But some kernel devs (Ted
and others) don't agree. They reason that the desire to preserve all
meta-data isn't reasonable by itself.
I'm with Henrique on that one. I am more concerned with the amount of
non-Posix code that needs to go into this than preserving all attributes.
Shachar
--
Shachar
On 30/12/10 17:02, Olaf van der Spek wrote:
Got a project page already?
Watch this space. Actual code coming soon(tm).
https://github.com/Shachar/safewrite
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ
the same
thing. The only difference is that for strace it works.
I need someone who is either a ptrace expert, or who has a fresh set of
eyes and some patience, to help me look at it and figure out what I'm
doing wrong.
Thanks,
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 22 Aug 2010 16:33:24 +0300
Source: argtable2
Binary: libargtable2-dev libargtable2-docs libargtable2-0
Architecture: source amd64 all
Version: 12-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 03 Apr 2010 05:56:36 +
Source: privbind
Binary: privbind
Architecture: source amd64
Version: 1.2-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 23 Jun 2009 21:42:23 +0300
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source amd64
Version: 0.16-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 28 May 2009 14:46:43 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source amd64
Version: 0.15-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 20 Feb 2009 11:01:12 +
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.12-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 20 Feb 2009 11:25:27 +
Source: sshpass
Binary: sshpass
Architecture: source i386
Version: 1.04-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 20 Feb 2009 21:48:32 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.14-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh shac...@debian.org
Changed-By: Shachar Shemesh shac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 18 Oct 2008 08:13:59 +0200
Source: sshpass
Binary: sshpass
Architecture: source i386
Version: 1.01-2
Distribution: unstable
Urgency: medium
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 20 Aug 2008 11:43:51 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.12-3
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 15 Aug 2008 05:32:36 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.12-2
Distribution: unstable
Urgency: high
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
Hi all,
I am preparing an upload to Sid, with the intent of getting it into
Lenny, for a package of mine (to solve bug #493061 for fakeroot-ng, if
it matters). While working on it, I found out that the package also has
a FTBS twice bug, which resulted from empty lines (with no leading tab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 25 Jun 2008 05:26:53 +
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.11-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
William Pitcock wrote:
It seems like moving to grub for everything may be a good choice on the
archs where lilo is used.
Lilo has one killer feature that is totally missing from GRUB - the -R
option. It allows me to upgrade a kernel on remote servers, knowing that
if the upgrade fails, I
Fakeroot-ng is a clean reimplementation of fakeroot, using a totally
different technology. Fakeroot-ng uses the ptrace interface to track the
syscalls performed by the fooled program. This means fakeroot-ng is
immune to problems that may happen as a result of races, cross-library
interactions,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 11 Jun 2008 08:48:57 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.12-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 09 Jun 2008 16:02:31 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.10-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 09 Jun 2008 20:47:55 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.11-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 24 May 2008 06:51:59 +
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.10-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 15 May 2008 15:09:43 +0300
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.09-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 13 May 2008 18:51:25 +0300
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.08-2
Distribution: unstable
Urgency: high
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 11 May 2008 20:49:21 +0300
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.08-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 07 May 2008 19:54:52 +
Source: argtable2
Binary: libargtable2-dev libargtable2-docs libargtable2-0
Architecture: source i386 all
Version: 9-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 07 May 2008 21:05:14 +
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.07-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 12 Apr 2008 12:28:35 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.09-2
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 15 Mar 2008 15:21:55 +0200
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.09-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
to http://ftp-master.debian.org/REJECT-FAQ.html for details.
N:
This is the copyright file:
his package was debianized by Shachar Shemesh [EMAIL PROTECTED] on
Tue, 08 Jan 2008 20:27:55 +.
It was downloaded from http://sourceforge.net/projects/fakerootng
Fakeroot-ng is copyrighted (C) 2007
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 20 Feb 2008 16:32:47 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.08-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 06 Feb 2008 17:21:17 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.06-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 31 Jan 2008 14:47:59 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.05-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 22 Jan 2008 13:17:40 +
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.06-2
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 12 Jan 2008 20:08:06 +
Source: fakeroot-ng
Binary: fakeroot-ng
Architecture: source i386
Version: 0.04-2
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
Petter Reinholdtsen wrote:
And of course, it also make it possible to
dynamically order the scripts based on their dependencies.
When you said and of course, I thought you were going to say allow
scripts that have no inter-dependency to start in parallel. Having a
concurrency level of at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 09 Jan 2008 10:12:33 +
Source: sshpass
Binary: sshpass
Architecture: source i386
Version: 1.01-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 28 Nov 2007 16:21:09 +0200
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.06-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 19 Nov 2007 13:00:52 +0200
Source: argtable2
Binary: libargtable2-dev libargtable2-0
Architecture: source i386
Version: 7-2
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 18 Nov 2007 09:39:23 +0200
Source: argtable2
Binary: libargtable2-dev libargtable2-0
Architecture: source i386
Version: 7-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 18 Nov 2007 09:24:40 +0200
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.05-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
David Anderson wrote:
Therefore, question: how should I get from this situation to having a
working .deb (including the cross-compiled driver), while at the same
time playing nicely with Debian packaging policies?
In the general case, the problem is much wider. Let me give you an example.
David Given wrote:
You've got two major tasks ahead of you:
- - port gcc
- - port the kernel
- - cross-compile a basic userland
Nobody expects the Spanish inquisition.
Actually, there is one more major headache, which is porting a boot
loader. Probably uBoot or something similar.
Tim Hull wrote:
I knew about that, though it's not actually an official Debian
repository (to my knowledge).
If I were looking for a date that was tall yes compact, what would you
tell me? How about a date with fair brown eyes?
What you are asking for is a contradiction. There are only two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 10 Jul 2007 13:59:32 +0300
Source: privbind
Binary: privbind
Architecture: source i386
Version: 1.1-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 5 Jun 2007 16:34:16 +0300
Source: privbind
Binary: privbind
Architecture: source i386
Version: 0.2-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL PROTECTED
Russell Coker wrote:
On Tuesday 05 June 2007 16:52, Shachar Shemesh [EMAIL PROTECTED] wrote:
Package: wnpp
Severity: wishlist
Owner: Shachar Shemesh [EMAIL PROTECTED]
What benefits does this offer over authbind which has been in Debian for ages?
It uses a (I think) much more
Russell Coker wrote:
On Wednesday 06 June 2007 20:05, Shachar Shemesh [EMAIL PROTECTED] wrote:
What benefits does this offer over authbind which has been in Debian for
ages?
Before I begin answering your questions, the bug report has a link to
technical explanation of how privbind
Package: wnpp
Severity: wishlist
Owner: Shachar Shemesh [EMAIL PROTECTED]
* Package name: privbind
Version : 0.2
Upstream Author : Shachar Shemesh [EMAIL PROTECTED]
* URL : http://sourceforge.net/projects/privbind
* License : GPL
Programming Lang: C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 21 Nov 2006 22:40:10 +0200
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 0.19-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 29 Oct 2006 15:08:17 +0200
Source: bidiui
Binary: thunderbird-bidiui
Architecture: source all
Version: 0.7.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian Hebrew Packaging Team [EMAIL PROTECTED]
Changed-By: Shachar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 3 Nov 2006 10:31:11 +0200
Source: bidiui
Binary: icedove-bidiui
Architecture: source all
Version: 0.7.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian Hebrew Packaging Team [EMAIL PROTECTED]
Changed-By: Shachar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 16 Nov 2006 13:32:54 +0200
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 0.18-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 14 Nov 2006 16:13:36 +0200
Source: argtable2
Binary: libargtable2-dev libargtable2-0
Architecture: source i386
Version: 6-3
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar
Package: wnpp
Severity: wishlist
Owner: Shachar Shemesh [EMAIL PROTECTED]
* Package name: bitefusion
Version : 1.0.1
Upstream Author : JC3¸rgen Jacobsen [EMAIL PROTECTED] and Morten
Hustveit [EMAIL PROTECTED]
* URL : http://www.junoplay.com/
* License : GPL
1 - 100 of 121 matches
Mail list logo
