-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
bargtable2.
It seems that debhelper is not a friend in that regard, pushing me to
install to /usr/share/doc/libargtable2-doc. Am I missing some option
that would make that easy?
Shachar
-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
be
a smarter course of action.
Of course, I'm sure there are those who will find my mail offensive, and
will be most prudent in letting me, and everyone else, know about it. As
such, I promise to henceforth accept my own advice. This is my last
email on this thread.
Shachar
1 -
http
to refrain from jokes other will find offending. If you see such a
joke, please try to refrain from stirring the fire by saying it's wrong.
Just, you know, be adults...
Shachar
will crash with log if it
performs an operation that C/C++ considers to be undefined.
Have not tried it myself, but feedback would be great.
Shachar
[1] http://gcc.gnu.org/gcc-4.9/changes.html
, and
*every* Ͻ program that does not make use of the additional guarantees
(i.e. no C UB) is also a valid C program.
[…]
find a non-sucking name that is ISO 646 IRV,
Let's call it Cava.
If we didn't have C, we'd all still be writing in obol,.pasal and basi.
Oh, and Fortran, of course.
Shachar
, in the code. While it's perfectly acceptable,
in my eyes, to ask the compiler to help you find that bug, getting mad
at it for not doing so makes no sense.
Shachar
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
(or -Wextra). If
it isn't, I do think it should be. Just checked, and it is on for -Wall,
sort of. See http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html.
Shachar
-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
readable and less maintainable.
Both of those problems, again, translate to less secure code.
I, for one, accept the extra liability that modern optimizers provide in
exchange for the easier to maintain, more secure code they allow me to
write.
Shachar
way, but especially in everyday
code, where those undefined behavior allows GCC to save you lots of cycles.
Are you really sure you want to have slower code just so that your
corner cases are easier for you? How is that a reasonable trade-off to make?
Shachar
.
* No references to previous discussions, or other people's arguments
for/against systemd.
I believe in free discussion. As such, feel free to ignore these
suggestions, just as I'll feel free to ignore your email if you do so.
Shachar
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
not the case, the package would fail to
build, as gcc points to gcc-4.6.4.
Is there some better way to cause the system to use a C++11 capable
compiler?
Shachar
P.S.
I no longer have a PowerPC platform to test with, and qemu-user isn't
emulating deep enough for fakeroot-ng to work under
not the case, the package would fail to
build, as gcc points to gcc-4.6.4.
Is there some better way to cause the system to use a C++11 capable
compiler?
Shachar
P.S.
I no longer have a PowerPC platform to test with, and qemu-user isn't
emulating deep enough for fakeroot-ng to work under
-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
On 13/03/11 08:19, Ben Finney wrote:
Shachar Shemeshshac...@debian.org writes:
Personally, I think the code of conduct should be amended, along with
the list software.
While this shouldn't turn into a counting of popularity, I'd like to
register that there are people who think
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
On 22/02/11 19:54, Ben Hutchings wrote:
Judging by what you consider 'small bugs' in
https://github.com/Shachar/safewrite/commit/efafcd4260375a41257709c7eb5a8d6065366849
why should anyone trust their important data to this library?
Feel free not to use it/file bugs against it. Giving
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
Hi all,
I've promised to get a library out there, and here it is. The base URL
is https://github.com/Shachar/safewrite, and the actual code is at
https://github.com/Shachar/safewrite/blob/master/safewrite.c
This is not a formal release just yet (plus one function is still
missing
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 30/12/10 17:02, Olaf van der Spek wrote:
On Thu, Dec 30, 2010 at 3:51 PM, Shachar Shemeshshac...@shemesh.biz wrote:
I'm working on one under the MIT license. Will probably release it by the
end of this week. Will also handle copying the permissions over and
following symlinks
. 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
On 30/12/10 17:17, Olaf van der Spek wrote:
On Thu, Dec 30, 2010 at 4:12 PM, Shachar Shemeshshac...@debian.org wrote:
No. I was doing it as code to accompany an article on my company's site
about how it should be done. I was originally out to write the article, and
then decided to add code
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
is not important enough, I can upload a fix that
only handles 493061, and doesn't touch the double FTBS bug at all.
What should I do?
Shachar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Wednesday 13 August 2008 18:34, Daniel Burrows wrote:
On Tue, Aug 12, 2008 at 08:57:24PM +0100, Adeodato Simó
[EMAIL PROTECTED] was heard to say:
* Shachar Or [Sun, 10 Aug 2008 18:36:35 +0300]:
I am not suggesting this data will be put in with the package's
description,
Why not? I
. Or, if there are no matches to show it as locally
installed.
If there are multiple potential sources some kind of ordering may be
needed [1] as may handling of CD sets.
Cheers,
FJP
[1] 'apt-cache policy package' essentially already does ordering
--
Shachar Or | שחר אור
http://ox.freeallweb.org
On Tuesday 12 August 2008 22:57, Adeodato Simó wrote:
* Shachar Or [Sun, 10 Aug 2008 18:36:35 +0300]:
I am not suggesting this data will be put in with the package's
description,
Why not? I think (briefly) explaining some of the most relevant
recommends and suggests is a perfect use
that are actual dependencies and not recommendations or
suggestions, should not require this information for this same purpose but it
may be a good idea for different purposes that I'm not thinking about right
now.
Excellent week and fun at debconf!
--
Shachar Or | שחר אור
http://ox.freeallweb.org
-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
will get the original kernel after a few minutes
without asking a local hand to push the reset button.
Until Grub has something similar, removing Lilo entirely seems like a
bad idea to me.
Shachar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
be greatly appreciated.
Thanks,
Shachar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-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
of at least 2 should speed the start up considerably,
especially when packages are taking long to start mostly because they do
a sleep in wait for some hardware to settle.
Coming to think of it, maybe concurrency level of 2 is a little low.
Shachar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
-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
we can build this tiny
blob seems out of proportion.
I think we need a change in policy for handling cases where free
software requires free software in order to compile which is, non the
less, non buildable on the same platform.
Shachar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
that is already supported under Linux. Of course, the startup
code and everything else under the arch directory will still need to
be handled, but at least as far as the drivers are concerned, some work
may be saved.
Shachar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
. If that is where your interests lie, I suggest you have a look at
the debian-volatile repository.
Shachar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-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
1 - 100 of 125 matches
Mail list logo
