Package: wnpp
Severity: wishlist
Owner: Bdale Garbee
X-Debbugs-Cc: debian-devel@lists.debian.org
Package name: openrocket
Version : 23.09
URL : https://openrocket.info
License : GPLv3+
Programming Lang: Java
Description : Model Rocket Simulator
Package: wnpp
Severity: wishlist
Owner: Bdale Garbee
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: librnd
Version : 3.0.0
Upstream Author : Tibor Palinkas
* URL : http://repo.hu/projects/pcb-rnd
* License : GPL
Programming Lang: C
Back in December, I put sudo up for adoption via WNPP. The response has
been underwhelming. It was just pointed out to me that since I didn't
actually post something explicit about this on debian-devel, some who
might be willing and able to work on it perhaps are just unaware that
it's up for ado
Package: wnpp
Severity: wishlist
Owner: Bdale Garbee
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: jboss-vfs
Version : 3.2.15.Final
Upstream Author : JBoss, A division of Red Hat, Inc.
* url : http://www.jboss.org
* License : Apache-2.0
Package: wnpp
Severity: wishlist
Owner: Bdale Garbee
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: annotation-detector
Version : 3.0.5
Upstream Author : XIAM Solutions B.V. (http://www.xiam.nl)
* URL : https://github.com/rmuller/infomas-asl
* License
Package: wnpp
Severity: wishlist
Owner: Bdale Garbee
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: pyqt-distutils
Version : 0.7.3
Upstream Author : Colin Duquesnoy
* URL : https://github.com/ColinDuquesnoy/pyqt_distutils
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Bdale Garbee
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: openmotor
Version : 0.4.0
Upstream Author : https://github.com/reilleya
* URL : https://github.com/reilleya/openMotor
* License : GPL
Programming
Package: wnpp
Severity: wishlist
Owner: Bdale Garbee
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: scikit-fmm
Version : 2019.1.30
Upstream Author : The scikit-fmm team
* URL : http://packages.python.org/scikit-fmm
* License : BSD
Programming
Package: wnpp
Severity: wishlist
Owner: Bdale Garbee
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: ezdxf
Version : 0.14.2
Upstream Author : Manfred Moitzi
* URL : https://ezdxf.mozman.at
* License : MIT
Programming Lang: Python
Description
FYI, I just filed an RFA for amanda.
My tape autochanger died, won't be replaced, and this means that for the
first time in a couple decades I won't actually be using amanda myself!
Willing victims^h^h^h^h^h^h^hvolunteers should chase down the RFA in
WNPP then contact me directly to talk about it
On Thu, 2009-12-10 at 23:59 +0100, Benjamin Drung wrote:
> Am Mittwoch, den 09.12.2009, 09:34 +0800 schrieb Paul Wise:
> > On Wed, Dec 9, 2009 at 8:07 AM, Benjamin Drung wrote:
> > > Am Montag, den 07.12.2009, 09:03 +0100 schrieb Frank Lin PIAT:
> > >> On Mon, 2009-12-07 at 00:14 +0100, Benjamin D
> Now if only we could say positive things about people BEFORE they
> resign, wouldn't this be a better place?
+1E6
John, thank you for taking the time to write and post that note. I couldn't
agree more.
When Manoj and I joined the Debian project, there were only a couple dozen of
us, and
we
Manoj,
As one of the few people around who has been part of the Debian project
as long as you have, please accept my sincere appreciation for your long
history of meaningful contributions... and in particular your lengthy
and honorable service as our secretary!
You have earned and retain my imm
[EMAIL PROTECTED] (Barak A. Pearlmutter) writes:
> As a compromise that addresses some of the issues I would suggest the
> following: go with upstream, but add some convenience code, to whit:
>
> (1) Hot-wire tar to check an environment variable TAR_WILDCARD_DEFAULT
> and activate the --wildca
On Wed, 2006-06-28 at 10:36 +0200, Bill Allombert wrote:
> > Here, the only way seems to be putting an entry in NEWS.Debian (for
> > users script, ie things not under our control).
Good idea, Christian.
> In addition, I would suggest we reinstate the previous behaviour, but
> display a warning w
On Tue, 2006-06-27 at 13:09 +0200, Jeroen van Wolffelaar wrote:
> But on the other hand, according to the 'be strict in what you send,
> liberal in what you accept' mantra, it makes sense for tar to not create
> tarfiles which in the past have caused issues for certain programs while
> there's a p
The new tar behavior with respect to wildcards is not a change I
introduced just for Debian, it's a new upstream change that appears to
be quite intentional and well documented, as per this text from the tar
info docs:
The following table summarizes pattern-matching default values:
Members
n-devel is not high on my list right now.
> Bdale Garbee <[EMAIL PROTECTED]>
>amanda
>dump
Change made to both packages in my CVS for the next upload.
Bdale
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[EMAIL PROTECTED] (David Schmitt) writes:
>> 4.2) the package fails to build. This used to be a RC critical FTBFS,
>> but is not so anymore. The porter are responsible for fixing the bug and
>> uploading a fixed package to unstable, as they do now.
>
> Wouldn't it be better: "The porter are re
[EMAIL PROTECTED] (David Schmitt) writes:
> On Monday 14 March 2005 11:10, Rene Engelhard wrote:
>> pcc is barely at 98%. I don't think that barrier should be that high. We
>> *should* at last release with the tree most important archs: i386, amd64,
>> powerpc.
>
> Please, 98% is not high. It is j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Vince Mulhollon" <[EMAIL PROTECTED]> writes:
> I can't participate in the debate at that time and date. Will a log of
> the debate be available via http and if so, where?
Yes, I'm sure a log of the debate will be made available online after the
eve
I am unable to spend as much time updating the 'ntp' packages as they deserve,
and so I would like to find someone suitable to either join me in working on
them, or take them over outright.
There are a number of open bugs that need to be addressed, and I'm completely
unhappy with the current defa
[EMAIL PROTECTED] (Martin Schulze) writes:
>12. http://testdrive.hp.com/
Yes, this can be a good resource. I also invite anyone working on ia64
porting issues to the #debian-ia64 channel on irc.debian.org. There is very
little activity visible there, but people who can help are often lurk
aj@azure.humbug.org.au (Anthony Towns) writes:
> On Tue, Aug 27, 2002 at 01:40:09PM +0200, Michael Meskes wrote:
> > I was just told the script updating testing doesn't run at the moment.
> > Is that true? If so, is there a reason? Are we already in freeze? :-)
>
> It's running, but it's not doin
[EMAIL PROTECTED] (Don Armstrong) writes:
> If not, I'll just file a bug w/ patch.
That's the right thing to do for now, regardless.
Bdale
[EMAIL PROTECTED] (Colin Watson) writes:
> Generally speaking, Debian packages aren't relocatable anyway. Many of
> them (unavoidably) end up with paths compiled into binaries.
We may have to deal with this for things like allowing ia32 binaries to run
on ia64 systems... though so far, all of the
[EMAIL PROTECTED] (Tille, Andreas) writes:
> Could any kind soul please do the job or just poin to an ia64 box with
> installed build dependencies?
Done.
Bdale
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[EMAIL PROTECTED] (Mikael Hedin) writes:
> ogle doesn't build on ia64, and I don't understand what's causing it.
...
> The configure script stops when testing xml2-config, but the correct
> version is on the system.
This often indicates that the configure script is trying to run a small
test pr
[EMAIL PROTECTED] (dman) writes:
> It does, depending on the environment. If many users of a system have
> used "normal" vi for a long time, and you want to convince them to
> install vim instead, it better behave the way they expect.
Why do people insist on installing 'vim' as 'vi'? It isn't v
[EMAIL PROTECTED] (Lenart Janos) writes:
> On Sat, Dec 29, 2001 at 03:30:28PM +0100, Bas Zoetekouw wrote:
> > You wrote:
> > > As you might already have noticed Debian begun to bloat - so many
> > > unneeded, unused, unmaintained(!) packages.
> > > My opinion is that one DD alone couldn't upload N
[EMAIL PROTECTED] (Brian Wolfe) writes:
> Actualy, I believe that the mkisofs maintainer should have seen that a
> new option was created and notified the maintainers of anything that
> depended on mkisofs ...
That's pushing it, I think. I've had several experiences as a maintainer
where somet
[EMAIL PROTECTED] (Adam Olsen) writes:
> http://lists.debian.org/debian-devel/2000/debian-devel-23/msg01353.html,
> which says there's a lintian error/warning called
> "ancient-standard-version", which I believe can detect when a debian
> package is far behind the upstream version.
Nope, it t
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> But I think the point here is that the presence of a jillion normal
> bugs, unaddressed for years, constitutes a release-critical bug
While that's an interesting assertion, the real question is what it means to
"address" a bug. There are package
[EMAIL PROTECTED] (Wichert Akkerman) writes:
> Previously Steve Greenland wrote:
> > Stdout and stderr from the maintainer scripts. (This may be obvious, but
>> you didn't explicitly list it.)
>
> No, they should use debconf.
Regardless of whether packages are using debconf, I have wondered for *
[EMAIL PROTECTED] (Martin F Krafft) writes:
> i don't think a global solution is a good choice here. if i install
> bind9-chroot (hypothetically speaking), then bind9 should not possibly
> ever run non-chrooted again. this should be done via diversions.
Eee. Diversions are so, well, messy.
Fellow Debian folk.
Those of us who run autobuilders have started seeing more cases of a new
class of problem showing up in our buildd email that we'd like your help
resolving.
It is possible in the Build-Depends specification of a package to give
alternatives using syntax like:
libltdl
[EMAIL PROTECTED] (Rahul Jain) writes:
> maybe there should be meta-packages for packages that have embedded version
> numbers like that.
In the general case, yes. In this case, there is no need for one, since the
package in question is build-essential, and so need not be listed in a build
depen
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes:
> Bdale Garbee <[EMAIL PROTECTED]> writes:
>
> > It isn't *quite* that simple. Explicit build dependencies should only be
> > for packages that are neither essential nor build-essential.
>
> But it's en
[EMAIL PROTECTED] (Bas Zoetekouw) writes:
> If a package requires any binary package in order to be build from
> source, it must declare a dependency on that package.
It isn't *quite* that simple. Explicit build dependencies should only be
for packages that are neither essential nor build-
[EMAIL PROTECTED] (Herbert Xu) writes:
> > kernel where all options were compiled into separate modules so simply
> > choosing the right modules constructs the optimal kernel.
>
> Guess what, that's how the current 2.4 kernel images are constructed.
Well, not really. All of the drivers and othe
[EMAIL PROTECTED] (Roland Bauerschmidt) writes:
> Speaking of IA-64: Do we have a machine yet? AFAIK not.
Several Debian folk have acces of one kind or another to IA-64 hardware. I
am not aware of any IA-64 systems fully dedicated to Debian development.
I am in possession of an IA-64 box from H
AIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: can we get rid of -I entirely, please?
> From: Bdale Garbee <[EMAIL PROTECTED]>
> Date: Mon, 08 Jan 2001 09:18:51 -0700
>
> After lots of discussion on the Debian developer mailing lists, the
> solutio
[EMAIL PROTECTED] (Matt Zimmerman) writes:
> As you know, it's been eons since the last upstream gzip release.
On advice of the current FSF upstream, we moved to 1.3 in November 2000.
I think it is entirely reasonable to talk to upstream about this before
contemplating forking.
Bdale
[EMAIL PROTECTED] (Wichert Akkerman) writes:
> gzip --rsyncable, aloready implemented, ask Rusty Russell.
I have a copy of Rusty's patch, but have not applied it since I don't like
diverging Debian packages from upstream this way. Wichert, have you or Rusty
or anyone taken this up with the gzip
[EMAIL PROTECTED] (Brian May) writes:
> Does bind come with multiple libraries?
Yes. Four, I think.
Ok, I haven't looked at our policies for shared libs for a while, and I
obviously have some reading to do. Thanks for the warnings.
Bdale
It was just pointed out to me that there is a new RFP for bind9 packages
filed to the wnpp part of the BTS.
As the BIND package maintainer, I indicated many months ago my intention to
package BIND 9.X for Debian.
Unfortunately, the BIND 9.0.0 and 9.0.1 releases contained sources for
required
[EMAIL PROTECTED] (Adam Heath) writes:
> Bdale hates dbs, doesn't know what it is
I don't hate dbs. I just get annoyed when packages with complicated build-time
patching schemes won't build. My sense is that each of these schemes increases
the probability of build-time failures by deferring wor
[EMAIL PROTECTED] (Nicholas Lee) writes:
> Are there any thoughts to a chroot install option for bind?? Its not
> that hard to setup, but I wonder how it would fit into the debian
> policy.
I've been thinking about it after 9.1.0 releases, and after I add debconf
support. I don't run chroot'ed,
In article <[EMAIL PROTECTED]> you wrote:
> Bug stamp-out list for Mar 31 03:06 (CST)
> Package: bind (debian/main)
> Maintainer: Bdale Garbee <[EMAIL PROTECTED]>
> 61129 base: bind upgrade leaves two named's running
I see how this can happen in some odd cases.
I've built a package of bidwatcher, which is a tool for users of eBay, that
assists in placing and monitoring bids. I don't really want to maintain the
package, though, so I'm calling for a volunteer to package this for real and
upload it. I'm happy to provide what I've done so far, but it's just
I have packaged 'pcrd', which is a utility for controlling an Icom PCR-1000
radio receiver. It is probably mostly of interest to amateur radio folk,
and so will go in the hamradio section.
The upstream site for this package is
http://www.mv.net/ipusers/cdwalker/pcrd.html
The PCR-1000 it
In article <[EMAIL PROTECTED]> you wrote:
> I'm having some trouble, actually with a Cisco 6509 switch, but getting
> it to talk to 20 VALinux machines. My story:
Some folks at work saw similar weirdness with the negotiation on some HP
switch products, their solution was to configure the switch t
In article <[EMAIL PROTECTED]> you wrote:
> Package: bind (debian/main)
> Maintainer: Bdale Garbee <[EMAIL PROTECTED]>
> 59649 bind: Gives core dump
Closed by 8.2.2p5-9, now in potato.
> Package: inn2 (debian/main)
> Maintainer: Bdale Garbee <[EMAIL PROTECTED]&
In article <[EMAIL PROTECTED]> you wrote:
> It might be he wants to talk about -changes ? There he's right (and I do
> totally agree with him).
I'm not excited about a list per architecture, but I've often wondered if
only posting to the lists messages for uploads that include source might not
be
In article <[EMAIL PROTECTED]> you wrote:
You know, the whole concept of 'a release' is orthogonal to the way I think
about Debian. We've been through that before, too, and I understand the
various reasons that it's important for us to "make a release" from time to
time... but I doubt any of my m
In article <[EMAIL PROTECTED]> you wrote:
> After reading this nice diskussion with all it's aspects, I want to
> complete the mess and suggest a "distribution" called
> e.g. "progressive" beetween stable(frozen) and unstable.
I gather you haven't read the discussion of package pools in the archi
In article <[EMAIL PROTECTED]> you wrote:
> does anybody know, wether there are ideas or plans to make
> an Debian GNU/Linux especially for embedded and/or realtime
> systems, i.e. "Embedian GNU/Linux"?
The problem is that "embedded" covers such a huge range these days. I've
built several embed
In article <[EMAIL PROTECTED]> you wrote:
> Package: pilot-manager (debian/main).
> Maintainer: Darren Stalder <[EMAIL PROTECTED]>
> 59202 pilot-manager: Method "GetRecord" missing in SyncPlan
The pilot-manager package is quite useful even if SyncPlan doesn't work, which
I can neither confirm n
In article <[EMAIL PROTECTED]> you wrote:
> Package: sawmill (debian/main).
> Maintainer: Mikolaj J. Habryn <[EMAIL PROTECTED]>
> 59760 sawmill: Sawmill fails to load -- missing file
> /usr/lib/rep/0.11/i686-pc-linux-gnu/timers.so
This is filed against version 0.25-1. The version in potato is
In article <[EMAIL PROTECTED]> you wrote:
> Bug stamp-out list for Mar 10 03:04 (CST)
> Package: dump (debian/main)
> Maintainer: Bdale Garbee <[EMAIL PROTECTED]>
> 59935 dump: dump segfaults
A number of bugs have been fixed since the 0.4b12 snapshot that's in
In article <[EMAIL PROTECTED]> you wrote:
> tar -zxf control.tar.gz control ./control
You can also use
tar -zxf control.tar.gz *control
which does not produce an error, and extracts either one. This is the fix I
supplied for lintian when the tar upstream changed the way pathname whack
In article <[EMAIL PROTECTED]> you wrote:
> What do other think, and have you seen seeing the same runaway bug severity
> inflation I have?
Yes. Submitters seem to think that if they crank up the severity, the bug
will get more/quicker attention. At least in my case, that just isn't true.
I'm
In article <[EMAIL PROTECTED]> you wrote:
> Bugs are no longer deleted!!! We don't have a way for you to access them
> directly but there's an "official" location in the database where they're
> being archived. We're trying to decide how to serve them up... by
> requesting a bug number, obviousl
In article <[EMAIL PROTECTED]> you wrote:
> Package: dump (main)
> Maintainer: Bdale Garbee <[EMAIL PROTECTED]>
> 44061 dump: Appears to be unable to dump rev 1 ext2fses with sparse super
I'm not an expert on ext2 filesystem internals. If someone who is wants to
ha
Hi John.
I just read your LWN backpage letter, http://lwn.net/1999/0916/backpage.phtml.
I'm the Debian BIND package maintainer. I am aware of no intention on the
part of Debian to undermine the goal of a public key infrastructure centered
on DNS. We simply cannot ship the RSA code in our dist
I'm going to package the software used with the Planet Connect satellite
Usenet feed service. We've been using it for a while, but there was no
explicit copyright/license terms in the upstream sources. A new version is
in the process of being released, and the author has agreed to resolve this,
I would like to offer the following two packages for adoption or removal:
upsd- I don't use it, but others apparently do, and there are
no open bugs that I am aware of
jaztool - I don't use it, I'm not sure anyone does. Rumor has it that
a
In article <[EMAIL PROTECTED]> you wrote:
> I'm not the only one to be annoyed at the nag messages that are sent out.
> Can the script please be disabled.
Absolutely. I've asked before for the nag widget to be turned off, and I
strongly support turning it off now.
Yes, I have a couple of packag
In article <[EMAIL PROTECTED]> you wrote:
>> Given the BIND package will move to non-free in version 8.2 due to
>> the license on the RSA code used for DNSSEC, it's good to see an
>> alternative that will be in main... even if it's less functional.
> Is it possible to keep an older version of Bin
In article <[EMAIL PROTECTED]> you wrote:
> I wonder if s/o is already working on this or if it doesn't make sense
> to package it.
Given the BIND package will move to non-free in version 8.2 due to the license
on the RSA code used for DNSSEC, it's good to see an alternative that will be
in main..
In article <[EMAIL PROTECTED]> you wrote:
> I'll be at Usenix again this year
As will I. Flying in Tues evening, back Fri evening. Will, as usual, have
some of my PGP fingerprint slips of paper with me in case I run into anyone.
Bdale
In article <[EMAIL PROTECTED]> you wrote:
> Since the sources include an explicit copyright assertion but no explicit
> distribution license
The upstream maintainers indicate in email that the GPL is their choice, which
is wonderful news. Now that this is resolved, I'll upload a package to main
In article <[EMAIL PROTECTED]> you wrote:
> I suppose that we could go to a
> "release candidate" model during the freeze, but that's something for another
> discussion.
Of course, until we discuss this, we're doomed to perpetuation of the current,
incredibly broken freeze process. [shudder]
Not
In article <[EMAIL PROTECTED]> you wrote:
> Hmmm. swinstall (HP-UX native I think) seems to support dependencies.
> It's pretty ugly though and I don't know if there's a command line version.
Yes, you can drive swinstall from the command line. It's not pretty, but it
works.
Unfortunately, there
In article <[EMAIL PROTECTED]> you wrote:
:> 21884 libc6-dev: relative links between top-level dirs
: The upstream maintainer (Ulrich D.) insists that the relative links are
: correct and that making /usr a symlink to something else is "evil".
I'm not sure I completely understand what the lin
In article <[EMAIL PROTECTED]> you wrote:
: The latest version of the Debian web pages are complete.
I like them. Good work! A few nits.
The link on the developer's corner page that I think should go to the list
of developers instead brings up the xearth image. The "visit the sponsor"
image o
In article <[EMAIL PROTECTED]> you wrote:
: I see versions numbered 2.0.7 and 2.0.8 as release versions, because that
: is the way the upstream authors see them. The tarballs that appear before
: those releases are given numbers like 2.0.7pre1 specifically to indicate
: that they are NOT releases,
In article <[EMAIL PROTECTED]> you wrote:
: I was looking at the list of release-critical bugs and noticed some bugs
: were closed. A lot of those closed bugs are for packages that are still
: sitting in Incoming. I would like to remind people that you have to wait
: with closing a bug until the f
In article <[EMAIL PROTECTED]> you wrote:
It's too bad upstream developers are so diverse in their attitudes about how
to number things... such that we have to deal with stuff like this. However,
that's a fact of life.
: 2) Use the Epoch system for the purpose it was intended, and move libc6
:
In article <[EMAIL PROTECTED]> you wrote:
: Bdale Garbee <[EMAIL PROTECTED]> wrote:
:> Have you actually tried this and found something different?
: I've run ntpdate numerous times with xntp already running.
Hmm. I didn't think that would work. Learn something new e
In article <[EMAIL PROTECTED]> you wrote:
:> Any reason not to use
:> ntpdate -b -s `awk '/^[ ]*server/{print $2}'` &
:> ? (that's a tab and a space between the square brackets).
:> [Note that I've tossed the timeout, but to prevent any potential
:> boot-hang problems have backgrounded the s
In article <[EMAIL PROTECTED]> you wrote:
: My personal opinion is that Apt is *already* the way to go.
Absolutely. 100% of the people I've suggested apt to (which is now almost
everyone in my circle of Debian friends) has switched to it for good. I have
had several people tell me that the apt
In article <[EMAIL PROTECTED]> you wrote:
: What will you record as fixing-version ?
If we reorganize the server the way I've been discussing recently, this
problem would go away... because no package could ever get into a stable
tree without going through unstable... one version stream should
In article <[EMAIL PROTECTED]> you wrote:
: Also its been suggested that the BTS not delete bugs, but store them
: in some kind of long-term archive. Full-text searching couldn't hurt
: either. :-)
The approach we used at work is that bug closure causes the file to get moved
to a different dir
In article <[EMAIL PROTECTED]> you wrote:
: I've had it packaged since the first week of January, actually -- just
: never uploaded it because its too flaky even when using its own copy
: of perl4 (included with the package, stolen from Ian's home dir). It
: seems that two files, process and erro
In article <[EMAIL PROTECTED]> you wrote:
: We need to think about what kinds of thing need to happen to a package
: or to a distribution before we release it as `stable'.
Yes.
I find it impossible to completely divorce the conceptual model from any
reference to details of the present or any pro
In article <[EMAIL PROTECTED]> you wrote:
: ... lintian flags the 'mx' and 'ns' commands as possible namespace pollution.
Ok, I'm convinced. The 8.1.2-2 package still includes these commands, and I
will leave them in indefinitely.
Bdale
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
Am working on the release-critical bugs in bind. It appears that lintian flags
the 'mx' and 'ns' commands as possible namespace pollution. These, along with
'', 'soa', and 'zone' are symlinks to 'host' that do quickie lookups for
those types of records, without having to specify an option lik
In article <[EMAIL PROTECTED]> you wrote:
: Personally, I have stopped using all the dselect methods in
: favour of the apt method for dselect.
Absolutely!
We've put apt on every machine in sight, and it's amazing how much different
dselect seems with apt-get layered between it and dpkg.
In article <[EMAIL PROTECTED]> you wrote:
: I'd like to see a Zip disk install set. What should go on it?
Heck, I have test systems with what I think are very functional installs that
run on 85 and 100meg disks... should be able to do a rousingly useful
standalone/install image on 100meg...
I'
In article <[EMAIL PROTECTED]> you wrote:
: Finally, realize that packages-wise, we probably rival RedHat's Alpha
: port---something on the order of 800+ packages are available on the
: Alpha. However, that's *half* of the number available in Debian/i386.
That raises an interesting question, tha
In article <[EMAIL PROTECTED]> you wrote:
: Yes, I know it may be too late to be changed, but are there any hints whom
: to contact to get this "fixed"?
The upstream maintainer, of course. Read the /usr/doc/tar/README.Debian file.
Also, note that if you pipe tar's output through cat or dd on th
In article <[EMAIL PROTECTED]> you wrote:
: with MAKEDEV -I you can create device files in the local directory,
: even within fakeroot. what about adding a list of the normal devices to cruft,
: and report obsolete devices, strange permissions, etc. this would require
: some cooperation with the m
In article <[EMAIL PROTECTED]> you wrote:
: fast. Its not agood solution, so thats why I asked here about
: integrating bzip2 support into gzip.
Points well taken. You're just asking in the wrong place. You should take
this up with the gzip upstream maintainer. It is not a Debian packaging
is
In article <[EMAIL PROTECTED]> you wrote:
: Hmm... it's actually probably a good idea to bzip2 the X sources.
: They're monstrous.
Probably a good idea. However...
The right way to handle this is for someone to broach the subject of using
compressors other than gzip for source packages over on
In article <[EMAIL PROTECTED]> you wrote:
:> Debian tar has a patch which hands off files to bzip2 if the -I option is
:> passed to it.
: Why wasn't the -z option expanded to recognize the bzip2 signature?
: That would seem to be a better solution to me.
Because the options are used both on comp
In article <[EMAIL PROTECTED]> you wrote:
I'm the tar maintainer for Debian, among other things.
: -z filter through gzip, bzip, bzip2 as appropriate
: That would be a nice thing.
But really hard to get right for compression. :-) For decompression, it is
conceivable that you could pick t
I intend to package 'jstation' for Debian. This is a suite of Java-based
software that implements a full-featured ground station for amateur radio
satellites using the Pacsat protocols.
Because jstation depends on JDK 1.1, it will go to contrib despite being
GPL'ed itself. This might change
In article <[EMAIL PROTECTED]> you wrote:
: Anyone have a digitized copy of this? :)
Look on www.npr.org later tonight. The 'current' page still has the pieces
from the 7th... All the interesting stuff on NPR becomes available via
RealAudio shortly after broadcast.
Bdale
--
To UNSUBSCRIBE, e
In article <[EMAIL PROTECTED]> you wrote:
: Given the creation of a bo-updates directory for those of us who wish to
: provide backported versions of hamm packages for bo (thanks Guy!), we now
: have the possibility to do this.
I'd encourage the packaging and release of a fresher xntp3/xntp3-doc
1 - 100 of 140 matches
Mail list logo
