No pills, no pumps - Its the Patch
http://www.siratu.com/ss/
Talk of nothing but business, and dispatch that business quickly.
A desk is a dangerous place from which to watch the world.
Toughness doesn't have to come in a pinstriped suit.
It is a profitable thing, if one is wise, to s
the
traditionel origines.
I am looking for traditionel music of the west side of Africa to find
out relations with Javaneese music and for North-east African music to
find out relations with Thai music.
Could you help me?
Thank you on forehand
regards
Peter Paul Seelig
--
To UNSUBSCRIBE, email
ou too stop serving
these users? I would upgrade to Debian 7 or 8 in the blink of an eye if
it offered a full-featured desktop menu.
--
Peter
pe...@bratton.ca
Hi,
There is no poppler-utils-dev package.
https://sources.debian.net/src/pdftohtml/ refers to etch
and sarge, which are somewhat outdated.
What pdftohtml source is appropriate for jessie?
Thanks, ... Peter E.
--
123456789 123456789 123456789 123456789 123456789
GooString is referenced in pdftohtml.cc. What is its purpose
or purposes?
Thanks,... Peter E.
--
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +13606390202 http://easthope.ca/peter.html Bcc: peter at easthope. ca
--
To UNSUBSCRIBE
On 04/05/2022 19:43, Russ Allbery wrote:
I don't know if it currently does this, but it would be useful for popcon
to show counts for public third-party packages that aren't in the archive.
See
https://popcon.debian.org/unknown/by_recent
Cheers,
Peter
Package: wnpp
Severity: wishlist
Owner: Peter Blackman
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name : c-evo
Version : 1.2.0
Upstream Author : Jiri Hajda
* URL : http://www.c-evo.org/ https://app.zdechov.net/c-evo/
* License : GPL2+
Programming
Package: wnpp
Severity: wishlist
Owner: Peter Blackman
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: xbrzscale
Version : 1.8
Upstream Author : Przemysław Grzywacz Zenju
* URL : https://github.com/atheros/xbrzscale
https://sourceforge.net/projects
Package: wnpp
Severity: wishlist
Owner: Peter Wienemann
X-Debbugs-Cc: debian-devel@lists.debian.org
Package name: python-imapclient
Version : 3.0.1
Upstream Author : Menno Smits
URL : https://github.com/mjs/imapclient
License : BSD-3-Clause
ttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997948
Regards,
Peter
Package: wnpp
Severity: wishlist
Owner: Peter Pentchev
X-Debbugs-Cc: debian-devel@lists.debian.org, team+pyt...@tracker.debian.org,
r...@debian.org
* Package name: python-test-tunnel
Version : 0.1.1
Upstream Contact: Peter Pentchev
* URL : https://devel.ringlet.net
about upcoming hardware upgrades and other improvements to
address these issues at
https://salsa.debian.org/salsa/support/-/issues.
Which particular issue here relates to the planned hardware upgrade?
Regards,
Peter
close it once it is fixed?
Agreed. I can't reopen it myself, buy maybe you could as reporter.
Perhaps people might provide as comments further insights about the issue.
More likely if its open.
Regards,
Peter
Zutils is a collection of utilities for dealing with any combination
> > of compressed and non-compressed files transparently. Currently the
> > supported compressors are gzip, bzip2, lzip, xz, and zstd.
There are also acat in the atool package, and bsdcat in
the libarchive-tools package.
G
Alexander Wirt wrote:
Hi guys,
I found some time to set up a rss feed for the dwn, try:
http://people.debian.org/~formorer/dwn/dwd.rss
Great work.
But your link has a typo. Try this one:
http://people.debian.org/~formorer/dwn/dwn.rss
--
Peter Hoffmann <[EMAIL PROTECTED]>
On Thu, 02 Dec 2004, Charles Fry wrote:
> > On Thu, Dec 02, 2004 at 05:59:09PM -0500, Charles Fry wrote:
> > > > In what ways is this package different to, say, dirvish, which I use
> > > > in a manner which is, AFAICS, identical to the way this package
> > > > operates?
> > >
> > > glastree prov
to the terminal, but one can easily imagine a tool
that would convert to a user's local character set when possible.
I suggest that the affected source packages[3] be run through the
command 'iconv -f ORIGINAL_CHARSET -t utf-8' as soon as convenient.
Would people support a mass bug
[Peter Samuelson]
> I suggest that the affected source packages[3] be run through the
> command 'iconv -f ORIGINAL_CHARSET -t utf-8' as soon as convenient.
Ehhh, I see I have already ruined my credibility by pasting the wrong
source package list. The real list is much shorter.
development *already* have to
know a modicum of English - and thus, non-ASCII variations on the Roman
alphabet should not confound most of us in the way other writing
systems might.
In either case, at least the email address will be a clue, and a point
of contact.
Peter
signature.asc
Description: Digital signature
nd debian/changelog to
be the same - I'd agree.
I'll wait for more feedback before doing it, though. One thing I don't
wish for is a public flogging for filing an unjustified mass bug.
Peter
signature.asc
Description: Digital signature
managers still do not provide .desktop files.
Please bcc me any replies replacing "no.spam" with "doc.ic.ac.uk" as I
am not subscribed to the list and do not wish to receive spam.
--
Peter
[Thaddeus H. Black]
> Would Peter permit me a mild dissent? I prefer Latin-1.
Dissents are fine. (:
The reason to go with UTF-8 is for consistency. Tools that wish to
render text onto the screen ought to be able to depend on knowing the
encoding that text is in. See below for why I (and m
On Mon, Dec 06, 2004 at 07:34:45PM +0100, Bill Allombert wrote:
> On Sun, Dec 05, 2004 at 03:54:12PM +0000, Peter Collingbourne wrote:
> > Hi
> >
> > I notice discussion on bug #241554 regarding a menu-method for .desktop
> > files used by KDM/GDM for window manager
rect
encoding for its LC_CTYPE is no harder than fixing it to make it accept
iso-8859-1 and spit out the correct encoding for its LC_CTYPE.
And if the app already deals with charset conversions but assumes
iso-8859-1 input, then it's trivial to fix it to assume utf-8 input.
Peter
signatur
[Roger Leigh]
> I've been using Debian with UTF-8 only locales for over 12 months
> now. I now consider it fine for general use, with respect to
> terminal and application support. Unlike a couple of years ago, most
> things work perfectly.
Some apps like 'screen' do not just configure themselv
On Tue, Dec 07, 2004 at 03:35:45PM +0100, Bill Allombert wrote:
> On Mon, Dec 06, 2004 at 11:47:16PM +0000, Peter Collingbourne wrote:
> >
> > This is a good start, now the question is how to integrate this into
> > the system.
> >
> > To tell you the truth I ha
Chasecreek Systemhouse wrote:
> Its a Accounting/Ledger system from http://www.sql-ledger.org/ --
apt-get install sql-ledger
re about 1/4 right. Or, being charitable, if you really meant
"*only* the Consistency part of ACID" when you said "ACID consistency",
then you were right but quite misleading.
Peter
signature.asc
Description: Digital signature
, think about how most people use xdvi.
Firmware files are not the sort of thing people can create their own
versions of. In most cases the format is not documented and there
are no free or even publicly available tools for this, and even in
cases where it *is* documented, this
> >even in cases where it *is* documented, this is not by any
> >stretch of the imagination a typical use case.
[Peter 'p2' De Schrijver]
> That's not true. Firmware can created by anyone and requires only
> documentation and a compiler/linker for the
On Thu, Dec 09, 2004 at 10:04:53PM +0100, Philippe De Swert wrote:
> Hello all,
Hi,
My eye just caught a few small items. For the rest, this is plain good work,
Peter
> (e.g. reverse engineering, porting too (and adapting of) comm
On Tue, 08 Feb 2005, Christoph Hellwig wrote:
> On Mon, Feb 07, 2005 at 01:24:25PM -0800, Oliver Kurth wrote:
> > Wrong.
> > - the orinoco drivers use eth
> > - the hostap drivers use wlan
> > - madwifi uses ath
> > - at76c503 uses wlan
>
> none of the drivers you mention as not using eth%d are i
[Tollef Fog Heen]
> Assume makes an ass of u an' me.
Why do people keep circulating this saying? It makes no sense.
Normally, assuming only ever has the power to make an ass of the person
who did the assuming, i.e. "me", not "u and me". And even then, it's
not like you could get very far in lif
On Mon, 14 Feb 2005, Henrique de Moraes Holschuh wrote:
> > Why? What argument is there against a per-release key, including
> > keys for security, testing, unstable, and experimental? It would
> > certainly make things a little easier...
>
> You still need to deal with key revocation and a new k
that could be trivially
added should people feel the need.
As should be obvious, I'm not a C++ hacker, so let me know what needs
cleaning and fixing. It works for me at least :)
I think this patch should be applied to apt before it goes into sarge,
as it makes some key issues easier to deal
(which is a
> problem on *all* non-i386 platforms).
I'd add unaligned data access (broken or at least problematic on most
non-i386). Again, though, it's not something s390 or mipsel have
special problems with.
Peter
signature.asc
Description: Digital signature
[Henrique de Moraes Holschuh]
> Not from what I know of dist-cc. You just need dist-cc, and nothing
> else. dist-cc just offloads the number-crunching, so it uses no data
> from the non-master node. AFAIK anyway (which is NOT much on dist-cc
> matters).
Right. distcc runs the C preprocessor o
mirrors), that's a problem for rsync/zsync to solve. Of course,
that doesn't help with buildd time, which is still a bottleneck in
certain cases.
Peter
signature.asc
Description: Digital signature
rsyncs the
uncompressed version. No reason it couldn't be made a bit smarter so
as to look inside the components of a .deb ar file. This being a
fairly interesting use case for zsync, I expect it's already being
considered, if not implemented.
Peter
signature.asc
Description: Digital signature
On Sun, 27 Feb 2005, Julien Danjou wrote:
> * Package name: wmail
> Version : 2.0
> Upstream Author : Sven Geisenhainer <[EMAIL PROTECTED]>
> * URL : http://dockapps.org/file.php/id/70
> * License : Seems specific, but free and probably GPL-compatible
> Descri
[Goswin von Brederlow]
> Which also avoids that packages will be unavailable on every new
> architecture debian introduces because the maintainer has to adjust
> the Architecture: line.
I suppose it'd be nice to be able to use !foo in the Architecture: line
for cases where something is known not
ions were involved.
Two, even if ALSA drivers were perfect, upgrading a working
configuration that uses OSS to a kernel that only provides an ALSA
driver for your hardware is just one more avoidable upgrade hurdle.
Peter
signature.asc
Description: Digital signature
[Blunt Jackson]
> I am familiar with the nss issue, although that's not really relevant
> to this question. The nss issue, and the related question in the FAQ
> is that when statically linking to libc, there are still dynamic
> loads required -- but libc handles this for the application.
> (Presum
aticly and the system
libraries dynamically is probably a good plan - if you need anything
static at all.
Peter
signature.asc
Description: Digital signature
blems I am having trying to get the next upstream version
to work properly.
--
\\//
Peter - http://www.softwolves.pp.se/
I do not read or respond to mail with HTML attachments.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
sive
effort into it.
It might also be easier to implement a new, less crufty, command line
shell (and programmatic interface to standard command line tools) from
scratch while one was at it.
--
Peter Eckersley
Department of Computer Science & mailto:[EMAIL PROTECTED]
I
[Christopher Crammond]
> Suppose you have a repository stuffed full of binary packages, in
> this case Debian Packages. If you were unlucky enough to have them
> in a rather un-organized fashion, I was just wondering if the package
> file itself would provide said information to allow me to write
[Alexander Schmehl]
> Curently it's quite easy to run unstables lintian, debootstrap and
> pbuilder on system running stable for the other packages. So I don't
> see a big problem creating and testing packages on a stable system.
It would make more sense to me to run lintian *inside* pbuilder, t
[Steve Langasek]
> python-dev provides an interface that packages can build-depend on
> which gives them both /usr/bin/python, and a set of development tools
> from the corresponding version of python. This is not analogous to
> petsc-dev, which only depends on the versioned -dev package.
The on
[Nathanael Nerode]
> Put it in the .diff.gz. If it's too large for that to seem
> reasonable to you, then you proabably shouldn't put it in your
> package. :-)
Heh, and how large is that? The combined effect of 'configure' and
'**/Makefile.in' can look pretty formidable, yet people exist who
c
[Anand Kumria]
> - require the developer to generate a new key
> - require the developer to have _at least_ N
> number of other, existing developers sign
> their key
> - once the devel
[Enrico Zini]
> My hope is that if more people start to use it, then package managers
> can start building features with it.
I thought that Enhances is merely the converse of Suggests, and that it
was invented for situations where it is problematic or inconvenient to
use Suggests directly, as whe
[Andreas Orfanos]
> I hope I post this to the right list.
debian-user is probably the right list, actually.
> The delay was not due to lots of new modules, it was clear that the
> incremental list of compiled components on the screen was moving up
> slow. I remember kernel builds where ultra fas
[Henrique de Moraes Holschuh]
> Hmm... wasn't the situation around this bug cleared up in another
> d-devel thread no more than two or three days ago, and a fix already
> commited to CVS?
That's what I thought. But the bug is still open. And jvw's reasoning
that it is OK for ftp.debian.org to c
[Erinn Clark]
> Yet just today you filed a bug (#340403) for documentation to be
> included in the package since you were unable to explain dpkg-sig's
> strengths. How is it possible for you to claim something is more secure
> when you don't understand it well enough to say how it's different?
Th
[Goswin von Brederlow]
> > Use 2: I have this Ubuntu CD and want to know which debs are from
> >debian and which got recompiled
> >
> > Look for all debs that have a deb signature of the debian archive
> > (to be added to dinstall at some point).
[Matthew Garrett]
> The answer is "
Steve Langasek wrote:
> * Use Debian's libtool.
I took one affected package (kmldonkey) from your list, relibtoolized
it as described, and rebuilt it, which failed spectacularly. Then, I
took another one (rekall), relibtoolized it, rebuilt it, and that
failed with a strikingly similar pattern.
k
[Steinar H. Gunderson]
> All three might eventually be truly broken, but you can bet that MD5
> will be the first to go. If you use SHA-256 today instead of MD5, you
> probably buy yourself a few extra years, which you can use to smooth
> out the transition to the next hash function when the world
[George Danchev]
> Even using weak hash sum algorythms you can easily make the hash
> collider life tremendously difficult by simply having more than one
> (ok two should be enough) hash sums generated with _different_
> (weak?) algorythms on the same entity.
What you have just defined is a new h
[Wesley J. Landaker]
> As described by the upstream website (the rest of this is a quote):
>
> What is sendcard?
> Sendcard is a multi-database (It currently supports 9 different
> databases!) e-card or virtual postcard program written in PHP. Suitable
> for large or small sites, it is very easy
[Lior Kaplan]
> * Package name: culmus-fancy
> Description : Type1 Fancy Hebrew Fonts for X11
I understand that the 'culmus' package already exists, and other
packages like 'lmodern' don't follow any particular name convention
either, but could you consider naming this thing t1-culmus-f
[Florian Weimer]
> > It should be replaced with "-". Beyond alphanumerics, only ".",
> > "_", "-" are in the POSIX portable filename character set[1], and
> > some systems do not allow the character "+" in file names.
[Henning Makholm]
> However there are already plenty of files with "+" in th
[Anthony Towns]
> gnupg comes close to being this, except for two things: it's got too
> many dependencies, and it's command line arguments are overly
> complex. A "gpgh" variant (like gpgv but for hashing) might work,
> though. It doesn't support --check, and "gpg --print-md md5
> /etc/motd" has
First of all, let me cast my vote for -doc-XX rather than -XX-doc. It
makes much more sense from a sorted package names point of view, which,
as others have said, is important in package manager UIs.
[Norbert Preining]
> texlive-documentation-czechslovak texlive-cs-doc
Czech and Slovak are two
[Adam Heath]
> > File: foo%20bar/hellurei.txt
> > Size: 12345
> > MD5: 012345667
> > SHA-256: 0a0a0a0a0a0a0a0a0a0a0a0a
> > Mode: 0644
> Checksum:
> md5: 0123456789[B
> sha-256: 0a0a0a0a0a0a0a0a0a0a0a0a
Checksum: md5: 01230123012301230123012301230123
C
[Frank Küster]
> > Why do we need two packages containing the "latex" command, for example?
>
> Why do we need N packages that provide MTA functionality?
That's not equivalent. An equivalent question would be more like "why
do we need N packages all containing the source code for exim and
build
Has the tech-ctte decision regarding the output format of md5sum [0] been
withdrawn in some form? It seems to be back to the old format:
$ md5sum http://lists.debian.org/debian-ctte/2004/06/msg00032.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? C
[Roberto C. Sanchez]
> Is there a way to not allow changelog entries to automatically close
> bugs assigned to other packages?
This has been suggested before; the standard counterargument is "what
about closing an ITP?"
signature.asc
Description: Digital signature
[Hans Hagen]
> how about a package (zip or rpm) with 'goodies'; since user are
> willing to install other non-free stuff (acrobat reader and such)
> they probably also hav eno problems with les-free goodies
It's not OK to violate someone's copyright just because users don't
mind things which are
[Russ Allbery]
> Maybe the right thing to do would be to work out a way for package
> maintainers to provide input to their own P-a-s entries in some sort
> of automated fashion? It does seem like a package maintainer is
> generally going to know this sort of thing
Could be done, but my understa
ting M == 0. It doesn't even look good in legacy
frontends. And as you say later on a related subject:
> Furthermore, fixing the description in this case is trivial.
Peter
signature.asc
Description: Digital signature
[Daniel Burrows]
> (1) The first line begins with N >= 2 spaces,
> (3) Each subsequent line begins with at least N + 2 spaces.
Hm. That brings up the minor point of whether N should ever be
anything but (2 * nest_level).
I don't feel strongly about that one, though.
Also, in the Best P
[Peter Samuelson]
> Hm. That brings up the minor point of whether N should ever be
> anything but (2 * nest_level).
Or if you consider nest_level to be zero-based, (2 + 2 * nest_level).
It occurs to me, though, that some might prefer the raw presentation
look of (2 + 3 * nest_leve
[Thomas Hood]
> After installation you should have a tmpfs mounted on /run. This has
> been created for the use of that handful of packages that need a
> place to store run time state files independently of networking.
Given the need, and now the reality, of /run, is there any need for a
separat
[Steve Langasek]
> Given the reality of /lib, is there any need for a separate /usr/lib?
>
> The principle is the same: /lib is used only for the minimal system
> required for booting, and everything else should go in /usr/lib.
> /run should be used only for junk that needs to be stored early in
On Sat, Dec 17, 2005 at 10:23:54PM -0800, Eduardo Silva wrote:
> As a lurker to debian-devel, I would like to point to
> all a deficiency in the current KDE way of naming
> menus, and hope that if Debian menu goes this way, it
> should improve on it.
>
> The current way KDE names programs is:
> Ty
erloaded
in the FHS to mean libraries, executables and data does not excuse
putting, effectively, temporary files there.
If anything, /etc/run, since /etc used to be the preferred dumping
ground for things which have now moved to /dev/shm (ick) and /run.
Peter
signature.asc
Description: Digital signature
[Thomas Hood]
> Any other defenders of /lib/run? Of /run?
/etc/run. mtab and resolv.conf and the lvm1 state files and so forth
always lived in /etc before, so there's continuity.
signature.asc
Description: Digital signature
[Miquel van Smoorenburg]
> I tested this and it works fine. It's also a better solution, since
> several packages contain directories in /var/run and ofcourse they
> expect them to still exist after a reboot.
That's a bug, IMO - they should mkdir -p in their init scripts if
necessary. It's not l
[Frank Küster]
> You are right - I was under the impression that this means "people
> who will do maintainer uploads of this package", but in fact it just
> says "maintainers" in the Policy.
Right, the field is misnamed, it should be "Maintainers:" but that
might be slightly confusing, visually.
[Brian May]
> Is there anyway you can disable this implicit shell, either with ssh
> or rsh? I really don't like it. I would rather each parameter be
> passed straight to the remote executable via exec without being
> parsed by sh first.
So you want rsh/ssh to do the job of word splitting? The q
What do you think about this request? It seems reasonable, but I think if
this should be supported, there ought to be a general policy (formal or
informal) on it because I think many other init scripts will suffer from
similar problems.
-- Forwarded message --
Subject: Bug#3
[Roger Leigh]
> In the case of someone who attaches a patch to a bug report, I think
> getting a mention in the Debian (or upstream) ChangeLog is
> sufficient.
Indeed, back in the days when reporting a bug and attaching a patch was
all I was willing to spend time doing, I thought a mention in the
[Peter Eisentraut]
> What do you think about this request? It seems reasonable, but I
> think if this should be supported, there ought to be a general policy
> (formal or informal) on it because I think many other init scripts
> will suffer from similar problems.
This issue was ment
[Steve Langasek]
> That's fine; I'm just saying that there's not much point in telling
> people to *not* ship /var/run (or subdirectories thereof) in their
> package.
Hmm, it should be noted that if you do remove /var/run/foo from your
package, you need to make sure the postrm deletes the directo
[Thomas Hood]
> Would it be useful if the initscript that clears /var/run also
> created a directory hierarchy under /var/run?
I cannot fathom how telling someone else to do a particular 'mkdir -p'
and 'chown' could possibly be simpler than putting the 'mkdir -p' and
'chown' into your init script
[Paul TBBle Hampson]
> Although as Steve Langasek has pointed out, the Sarge->Etch upgrade
> will be hard unless the etch key becomes available to Sarge users
> who've not touched their system since Sarge r0a... I guess this comes
> down to making the etch key available in some kind of Sarge-signe
[Stephan Hermann]
> Oh, I never signed an NDA, so I've never seen the code, actually I'm
> not interested in the code, because if I have a problem with the
> result, I can file bugs against this products, or bug the maintainers
> of the code in their present irc channel :)
It is clear that you do
[Martin Meredith]
> Thing is, in ubuntu - we don't neccesarily have "maintainers" for
> packages.
>
> We use a collaborative process - anyone who had access can modify the
> package. Basically - many many people can change a package, which can
> be confusing for people.
Here's the thing: the Mai
[Sami Haahtinen]
> like 'dpkg --show-primary-contact ' That way we could even
> add a separate field Preferred-Contact: (or something alike) that
> could override the maintainer and modifier.
"Preferred contact" is *exactly* what the Maintainer field means.
[Well, and the co-maintainers ("Uploade
(M-F-T set.)
[Frans Jessop]
> When somebody wants to become a DD he is told ?Go find a package to
> maintain, one that you can be the maintainer for.? I see serious
> problems with this approach as Debian increases in DD's. I will how
> this is in a second. What I think should be emphasized is
[Ken Bloom]
> $substvar{'Source-Version'}= $fi{"L Version"};
> +#Indep-Version is for supporting binary NMUs when a strict
> +#version dependancy is required against an arch independant package
> +$substvar{'Indep-Version'}= $fi{"L Version"};
> +#strip out the +bN format binar
[Adam M.]
> Instead of doing blind substitutions like it is done currently, it is
> possible to separate Arch:all from Arch:any|other|whatever in the
> substitution script such that,
>
> Source-Version => bin NMU version for binaries that are build
> Source-Version => 'original' version for Arch:
.
>
> As pointed out several times, the source package in the ubuntu archive
> is NOT different to the source package in the debian archive. The
> binary package have been rebuilt in an different environment, which
> can caus different dependencies on the resulting binary package.
You sai
e. We've got enough to
worry about just making packages suitable for Debian - why go out of
our way to help people who refuse to use Debian?
Peter
signature.asc
Description: Digital signature
[Thomas Bushnell BSG]
> Since you don't do bin-NMU's, you could simply alter the version of
> every package to add an "ubuntu" tag, and then be done with it,
> right? That would work well and be very easy to implement.
You are so hung up on this point, it's not even funny.
Do you really think u
[Jérôme Warnier]
> After the last update of OOo in Sid (aka Unstable), I wonder if it is
> generally considered acceptable to keep obsolete packages in
> experimental (currently, Sid has 2.0.1-2 and Experimental 2.0.1-1).
Hmmm, I thought experimental was garbage-collected automatically in
this ca
[Jérôme Warnier]
> Or even better: a list of all packages already installed on my system
> which have an experimental version?
There might be a better way, but assuming you have experimental in your
sources.list...
t=$(tempfile);
awk > $t '/^Package:/{print "^" $2 "$"}' \
/var/lib/apt/li
On Fri, 20 Jan 2006, Wouter Verhelst wrote:
> > > /tmp/app/1/image /tmp/app/1 cramfs,iso9660 user,noauto,ro,loop,exec 0 0
> >
> > Doesn't this introduce a local root exploit? A user can easily write
> > their own /tmp/app/1/image file which contains, say, a setuid root bash
> > executable.
>
[David Nusinow]
> As far as I understand it, this is simply grandfathered in. I'm not
> that up on the FHS details though, so I may be wrong. Remember also
> that this isn't X11R6 any more, but X11R7.
Branden toyed with the idea of setting ProjectRoot to /usr when
packaging XFree86 4.0. I was so
1 - 100 of 1909 matches
Mail list logo
