Package: wnpp
Severity: normal
I intend to orphan the gdb package. I will continue to intermittently
follow upstream development, and upstream is pretty active; not a lot
of Debian-local work is needed. There's a couple of local patches
(bad Dan!) which could be submitted. Or possibly dropped w
ex setup involved.
> I have a vague sense of what you are remembering, but common sense
> should basically sum it up. Is there no way upstream would accept
> doing this as a runtime plugin, that only gets used if it's there?
I have no idea. It would be a big pain to implement.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
optional dependencies should generally be enabled,
which had some special words about X11? I can't find it any more.
> Why don't we provide a gdb-tiny package, in the same fashion as
> vim-tiny? Or is the python support that much hardcoded into gdb source
> now that it ca
That saves you the really
grotty bits.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
led, as opposed to the 8MB+ that the main GDB package will grow
to in Lenny+1. Still not small.
It's a matter of stripping out the TUI, along with expat and Python
support. I'm not planning to do that without a good reason.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSC
On Mon, Jul 07, 2008 at 06:45:23PM -0400, Theodore Tso wrote:
> On Mon, Jul 07, 2008 at 06:16:22PM -0400, Daniel Jacobowitz wrote:
> >For various reasons we don't use it at work - instead we added some GCC
> >command line options to relocate the debug info at compile time. In
On Mon, Jul 07, 2008 at 06:01:15PM -0400, Theodore Tso wrote:
> On Mon, Jul 07, 2008 at 05:42:47PM -0400, Daniel Jacobowitz wrote:
> > I think they do this, using "debugedit". We (CodeSourcery) do it for
> > our libraries too. It's incredibly useful - but ver
On Mon, Jul 07, 2008 at 11:45:14PM +0200, Mike Hommey wrote:
> On Mon, Jul 07, 2008 at 05:42:47PM -0400, Daniel Jacobowitz wrote:
> > I wouldn't want them in the archive for everything, but it would be
> > nice to be able to generate automatically usable source packages.
>
tically expand macros in expressions and can
display them.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
was looking at the .gnu_debuglink section as created with
> objcopy?
Yes, but that just determines the basename to search for.
The places searched are $(dirname $origfile)/$debugname, $(dirname
$origfile)/.debug/$debugname, and /usr/lib/debug/$origfile.
--
Daniel Jacobowitz
CodeSourcery
--
T
debug packages without having to create them in debian/control
and debian/rules. That would enable build daemons to generate and
stash the packages somewhere if we decide to make them available.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
c patches, or
(more likely) hearsay. The difference between -g (same as -g2) and
-g3 is whether .debug_macinfo is generated - debug info for C/C++
preprocessor macros. It's off by default because the generated data
is huge.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to
On Tue, May 27, 2008 at 03:54:25PM -0500, Raphael Geissert wrote:
> Daniel Jacobowitz wrote:
> >
> > FYI, the most recent CVS snapshots of GDB can read zlib-compressed
> > debug info. If someone gets around to an objcopy patch to create it,
> > then we can
debug info. If someone gets around to an objcopy patch to create it,
then we can change debhelper to use it...
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
en the chance to resolve anything to it. You end up
with relative relocations or fixed PC-relative offsets.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d at gdb and objdump. Appears they
> need a complete object file. What tool can disassemble
> this string?
Try objdump -b binary -D.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
s in the original version are
correct and intentional :-)
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
t;
>
> 0 is not a pointer, hence disqualifies.
Just to confirm Kurt's point, 0 is a "null pointer constant" in C.
But it is not necessarily a pointer. You can't terminate a varargs
list of pointers (e.g. execl) with NULL unless you cast it.
--
Daniel Jacobowitz
CodeSou
this way would seem too much like me using it as
> a personal bludgeon.
You want to talk about appearances. It appears that you're acting as
inherently superior to another developer without involving the TC
because of the fact that you're already on it.
--
Daniel Jacobowitz
CodeSource
I would imagine it's in $HOME/.reportbugrc.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
enty of installations of
perforce; I think making it easier to use Debian with them is
within the mandate for non-free.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d package
> and just copy the binary blob from it.
>
> Any objections to this?
That's pointless. Why bother?
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I think this is the way to go unless you get some concrete objections.
There is certainly precedent - see for instance the ia32-libs /
amd64-libs packages (which are frowned upon for whole different
reasons).
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
ow long it
takes to crack a password - misses the point. If you enforce longer
passwords than people are comfortable with, you get weaker passwords
(or poor password management practices). It's the humans that matter,
not the machines.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIB
t think of one;
How about modern brain availability? You'll just get a lot of annoyed
people changing it back; for example, makepasswd still uses a minimum
length of six.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Jul 10, 2007 at 07:13:03PM -0500, David Moreno Garza wrote:
> Daniel Jacobowitz wrote:
> > When last I looked (some time ago), none of the different XMMS
> > successors were ready for prime time. Are bmpx, audacious, and xmms2
> > all usable now?
>
> What'
prime time. Are bmpx, audacious, and xmms2
all usable now?
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Apr 24, 2007 at 11:43:02PM +0200, Pierre THIERRY wrote:
> Scribit Daniel Jacobowitz dies 23/04/2007 hora 16:19:
> > Another possible way to change glibc would be to have libc6-dbg
> > contain full debug symbols, libc6-dev contain -g1 symbols only, and
> > have the
me only from BTS. May be we
> can learn from them as to what they are doing (mandatory registration?)
> better.
Unfortunately spammers seem to have learned how to register with
bugzilla, lately.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
to be able to do this, but it needs a little love and to be
integrated into the post-install process.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Apr 23, 2007 at 03:08:41PM -0400, Joey Hess wrote:
> Daniel Jacobowitz wrote:
> > Yes, it's deliberate. People rarely need them just because they're
> > debugging something linked to libc.so.6. Having them slows down GDB
> > startup and increases its
s with setting up[2]/maintaining the separate udeb section of
> the archive is that it adds a lot of complexity.
FWIW, I still think this is the way to go, though it would be hard.
They wouldn't need nearly as much mirroring. e.g. they could go into
a separate pool directory...
--
d.
You get extra information. What this output means is that it's not
enough debugging information to do line number mapping. That is
probably the maintainer's deliberate choice; check the source package.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL P
ssage "cannot execute binary file".
Just install it, don't try to run it. GDB will pick it up
automatically.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
happens several times, consider sending patches to the mailing
list or maintainer rather than responding to the bug submitter with
possibly incorrect information. This is the only major pitfall of
trying to help out.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
ithin the last year.
The release team uses it extensively.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
contains plugins which are linked to each library; the
plugins get dlopened, not the database libraries. This is pretty
typical for plugins.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, Dec 30, 2006 at 04:37:15PM +0100, Joerg Jaspert wrote:
> I personally would love, if you go and whitelist, that you also
> whitelist the following set of hosts:
Wouldn't this be useful in the greylistd configuration on master, then?
--
Daniel Jacobowitz
CodeSourcery
--
To
before by processing the
series file. But it's not pretty.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Nov 14, 2006 at 08:58:00AM -0500, Roberto C. Sanchez wrote:
> I understand that the line must be drawn somewhere. However, I am
> concerned about Etch shipping with a 2.6.17 kernel because of Xen.
Please read further down, to where the next rc is expected to include
2.6.18.
--
g code onto the stack which causes
the target process to open your terminal and dup2 it onto stdout,
stderr, et cetera. Interesting.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ix them are posted to this list
periodically.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
you can sit here and calmly assert
that a project as thoroughly designed and audited (and generally
respected) as SELinux is simply "more harm than good", whatever the
quality of the Debian-specific patches, and expect to be taken
seriously.
--
Daniel Jacobowitz
CodeSourcery
--
oblem. You should read the dmesg output to look for
> error messages there.
Actually, this particular I/O error has nothing to do with hardware; it
has to do with the kernel's "virtual DSO" page, if I remember right.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE
ply to libX11. Or can we do the compile for lib64, use
> lib trick there as it is not frozen?
I don't think it matters, but it's up to the X maintainers.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, Sep 23, 2006 at 10:29:37AM +0200, Goswin von Brederlow wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > On Sat, Sep 23, 2006 at 02:50:35AM +0200, Goswin von Brederlow wrote:
> >> But running Debian binaries on other distributions remains a
>
ectly happy to do this. After etch.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
l system whose
support for managing lots of individual patches all feeding into one
final result was as good as quilt.
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
f you can figure out where they go. The last time I had to adjust my
(CDBS-using) build process I wasted an hour grepping around in
/usr/share/cdbs.
I think what CDBS could really use would be an improved manual. The
examples don't cover a lot of things you can do with it.
--
Daniel Jacobowit
ne
Starting RAID device md2 ... 2/3 drives, degraded
Starting RAID device md3 ... 1/3 drives, failed
Starting RAID device md4 ... 3 drives, done
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e roughly ABI compatible, but they are neither license
compatible (you can link libelfg0 with whatever you please) nor
completely quirk compatible (I've reported bugs in using the elfutils
version to modify files where it would corrupt output, I have no idea
if they've been fixed).
--
Dan
e paths, etc.).
>
> It would be good to hear from the glibc maintainers if there are any
> issues addressing bugs such as: 345479, 351049 with an update for
> stable.
It's not us, but the stable maintainer, that you'd have to talk to;
he has traditionally not been interested in
nse; normally the license is in the source code,
not in the binary.
http://sourceware.org/ml/gdb/2005-12/msg00126.html
--
Daniel Jacobowitz
CodeSourcery
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, Dec 10, 2005 at 11:46:50AM +1000, Anthony Towns wrote:
> On Fri, Dec 09, 2005 at 10:19:46AM -0500, Daniel Jacobowitz wrote:
> > I'm not saying that this all needs to be publicly logged. I don't give
> > a rat's ass whether it is or not. But please don
handholding in the buildd system
configuration, et cetera.
I'm not saying that this all needs to be publicly logged. I don't give
a rat's ass whether it is or not. But please don't stand there saying
that the process is completely transparent.
--
Daniel Jacobowitz
CodeSourcery, L
n thinking about enabling it by default anyway, but it's the
sort of thing that needs to be measured first.]
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
nyway, to improve the quality of the upstream software.
>
> How should I proceed?
Another option is to either leave the information in the buildd log
files (i.e. send it to stdout), or to include test results in the .deb
files and retrieve them after the build. That latter is what the GCC
certainly, but you have to be able to pass them in a way
> which is understood in the C calling convention.
That's incorrect. The C++ ABI uses a defined convention for passing by
reference, and with a different prototype and some care, or from
assembly, you can duplicate the effect.
const char *
> > const argv[],
> > ostream& errstream,
>
> You must not pass by reference with an extern "C" declaration, because C
> doesn't support that.
Why not? An extern C definition do
tching the
> makefiles. i'd like a tool to modify this kind of things in the elf,
> probably elfsh is what i'm looking for. something to run after the
> build process. any idea?
In general you can't do this unless you're replacing it with a shorter
soname. I highly rec
ole addresses, too.
Whenever you write a message, you speak for yourself, in addition to
any group of people you represent. So I would appreciate it if you at
least signed messages with a name.
Thanks.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
ng
anything more complicated.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
binutils change which might in fact be completely
> innocuous is untenable as well.
Use binutils-dev, link to libbfd.a? The source API changes relatively
rarely, it probably won't bite you.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sun, Sep 18, 2005 at 11:52:09PM -0400, Daniel Jacobowitz wrote:
> Here's the code, hardcoded paths and all:
> http://return.false.org/~drow/fuse/shadow-etc.c
Slightly better, but not much:
http://return.false.org/~drow/fuse/
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To
enough for 32-bit firefox and OpenOffice.org.
I've got the feeling this could handle flock() locking correctly, but
doesn't - does FUSE even implement that? Anyway it should be fine
for /etc/.pwd.lock.
Here's the code, hardcoded paths and all:
http://return.false.org/~drow/fuse/s
, not the one that the library is linked against.
> Segfault.
Yes. Not, strictly speaking, a compiler bug. Versioned symbols are
not the right tool for solving this; however, the right tool for
solving it was presented in a paper at the last GCC summit. I believe
by some ICC developers. I don'
bove command from outside of the sid chroot works as
> >well.
>
> The reason is that findutils 4.2.2{4,5}-1 behave differently. (I don't
> know why exactly). If you change the -perm argument to
> -perm -u+x
> it works.
That means something different. There
On Mon, Aug 08, 2005 at 03:31:40AM +0100, Steve Kemp wrote:
> On Sun, Aug 07, 2005 at 10:12:56PM -0400, Daniel Jacobowitz wrote:
>
> > > The SSP compiler is a patch against GCC and offers "Stack Smashing
> > > Protection". In short it gives protection against
ch against GCC and offers "Stack Smashing
> Protection". In short it gives protection against buffer overflow
> bugs, and attacks.
Steve, you are aware that GCC 4.1 will include a complete
reimplementaton of this feature, right? Wouldn't time be better spent
with that
trips signatures?
Hmmm... same thing here.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
osting services". perhaps that did not
> happen?
You found out when we did.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Jun 17, 2005 at 03:58:35AM +1000, Daniel Stone wrote:
> Hoary (like sarge) is built against 2.3.2.
>
> Breezy (like current sid) is built against 2.3.5.
No, 2.3.5 is still in experimental.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
7;m behind a firewall).
This I don't know anything about, but it seems like a good thing to fix
instead of shoehorning LaTeX into the textual portion.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
l with
> the BTS ? Close the bug ? add a wont-fix tag ?
Make a version which generates the image on the sending side?
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, May 24, 2005 at 01:43:12PM +0100, Andrew Suffield wrote:
> On Mon, May 23, 2005 at 07:54:53PM -0400, Daniel Jacobowitz wrote:
> > > Because libbfd does not have a stable ABI suitable for public use, nor is
> > > there currently a way to express a dependency on
eaking (you can't depend on "binutils" and have any guarantee of
> getting the correct lib).
Does make me wonder why we ship libbfd.so and libopcodes.so, instead of
just the static libraries.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
lly surprised) to find two of my NEW packages being approved
> within just three days.
>
> Thanks a lot for your work, and for making Debian a more pleasurable
> place for developers!
That sounds like props, not like prods...
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRI
source packages instead. I just didn't have time to work on that
before sarge.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, May 09, 2005 at 02:33:32PM -0700, Thomas Bushnell BSG wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > On Mon, May 09, 2005 at 02:21:35PM -0700, Thomas Bushnell BSG wrote:
> >> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> >>
>
On Mon, May 09, 2005 at 02:21:35PM -0700, Thomas Bushnell BSG wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > The number of directory entries in /usr/lib should not make any
> > difference to a modern GNU linker on a modern filesystem, unless
> > you
to a modern GNU linker on a modern filesystem, unless
you have thousands or millions of them.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e been some problems with it, and they were fixed in
versions of binutils not yet included in Debian. I second Steve's
advice; if you want to use this ld feature, wait a little longer.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Mar 17, 2005 at 05:58:21PM +1000, Anthony Towns wrote:
> Daniel Jacobowitz wrote:
> >My basic idea is to have something similar to the testing migration
> >scripts, which takes the decisions of the "master" copy running on
> >ftp-master as an input. At a min
quot;powerpc" port; it
evolved. At the time, none of these issues existed, and powerpc seemed
like the logical thing to call it.
I think Andreas has given good justification for using ppc64.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
how many architectures will suffer
> from the _all dependency trap when maintainers don't care about crap
> architectures anymore that won't be released at all.
I imagine most of the ports would have their own copy of binary-all
in this scenario. Or additional binaries would
On Wed, Mar 16, 2005 at 06:57:56PM +1000, Anthony Towns wrote:
> Daniel Jacobowitz wrote:
> >I've suggested (briefly) a slaved testing which tries to enforce sync
> >with the main testing archive.
>
> Hrm, I don't think I've got any idea what that means.
I
testing which tries to enforce sync
with the main testing archive. Similar things could be done for
stable. It's been a long time since I was on the front lines of a
port, so I don't know how much manpower the ports have to work with
nowadays; but I bet they could manage this much.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Mar 14, 2005 at 07:51:05PM -0600, John Goerzen wrote:
> On Mon, Mar 14, 2005 at 08:14:47PM -0500, Daniel Jacobowitz wrote:
> > On Mon, Mar 14, 2005 at 07:02:05PM -0600, John Goerzen wrote:
> > > Really, I don't really understand all the difficulty of running
>
f these questions are too elementary or seem obvious to
> you, but it will help me understand better.
The only differentiating requirement for scc, as opposed to the other
"part of Debian" architectures, seems to be download share. That won't
suddenly change.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
the main "testing" - I haven't
considered the technical details of that in depth, but I'd bet it could
be done. Then, *poof*, a Debian/etch/Ports release is made!
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
n written, and we're starting the
submission process over the next couple of weeks, I hope.
--
Daniel Jacobowitz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Dec 09, 2004 at 04:42:29PM -0500, Ian Murdock wrote:
> On Thu, 2004-12-09 at 15:10 -0500, Daniel Jacobowitz wrote:
> > As one of the maintainers involved in Debian's toolchain, I think this
> > is a terrible idea. Our needs are different than other distributions,
>
er. My experience tells
me that would be a big barrier to certification of any kind.
There's plenty more than certification keeping Debian from standing
along side enterprise distributions in the commercial space.
If there is merit to the common binaries, I think we would get more
mileage from it by supporting them as we do the LSB: with separate
packages on top of the Debian base system.
--
Daniel Jacobowitz
version for development purposes.
See dh_strip --dbg-package for the correct way to do this now.
> Is there a policy which prohebit *.so files in /usr/lib/debug ?
> What is the real reason ?
>
> The same is for *-prof packages. There are only *_p.a files
> but no *_p.so.
Habit, I suppose.
--
Daniel Jacobowitz
nfs (2) umountfs in initscripts un-mounts filesystems, so
> >"mountfs" makes a name pair. Any comments?
> Looks good. OTOH, maybe it's not a good idea to pair mountfs with
> umountfs, as they operate on different kinds of file systems, so
> mountkernfs could
gt; What could be the error here? It seems to build fine on all other archs other
> than mipsel and mips.
This is normally a transient error; something got confused.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
he author hapens to be in my web of trust.
>
> What kind of real world attacks do signed debs prevent?
>
> The only one which comes to mind is a rogue Debian developer that you do not
> wish to trust, even though the project trusts him.
Someone pretending to be someone Manoj tru
es, IDE, and dual gigabit ethernet. MIPS, Inc.
has a similar board; Debian has one of these somewhere, IIRC. These
little fellows have more computing power than our PPC build daemon.
The machines you are likely to be thinking of are things like the SGI
R12000; the conventional workstation-ty
kernel-patch package for this
> patch? What should I call it? (I'm thinking kernel-patch-rtcap or
> kernel-patch-capability)
I would want considerably more information on the security implications
of allowing CAP_SETPCAP than either of those documents provides, if I
were you.
The POSIX cap
n.
Then your unstable mirror is broken. Might want to investigate that.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
1 - 100 of 178 matches
Mail list logo
