On Mon, Jan 10, 2005 at 09:51:54PM -0600, Matthew Dempsky wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > On Mon, Jan 10, 2005 at 05:17:19PM -0600, Matthew Dempsky wrote:
> >> It seems like the common case for wanting to install a kernel module
> >> source package is to build the module an
On Mon, Jan 10, 2005 at 11:07:52PM -0800, Steve Langasek wrote:
> in ways that were not backwards-compatible: automatically pulling in the
> -utils could render the system networkless before you've even started to
> *build* the modules...
In theory, yes if ndiswrapper-modules has a versioned depen
Once upon a time Scott James Remnant said...
> On Tue, 2005-01-11 at 11:15 +1100, Cameron Hutchison wrote:
>
> > dpkg first removes foo-modules_1.0
> > dpkg then check dependencies of foo-modules_2.0
> > dpkg complains that foo-utils is not installed and aborts the
> > installation of foo-modules_
#include
* William Ballard [Sun, Jan 09 2005, 10:12:13PM]:
> All:
>
> Some of you have probably seen my gripes about ndiswrapper-source.
> I moved on past all that -- but upstream is debianizing it and
> it's better in many ways.
Stop abusing Debian-Devel for your private wars and file a proper
* Joey Hess:
> Andrew Suffield wrote:
>>* New upstream release (closes: #270944, #277543). It's less than two
>> weeks since this was released; may you contract an interesting
>> venereal disease.
>
> Is this really called for in changelogs? Note that the bug reports were
> perfectly
* Steve Langasek:
[DJB's vulnerability research course]
> Considering the assignment AIUI was "find security holes",
I think the assignment was "find potential security holes and prove
that they are security holes, by writing exploits". The first part is
easy, just compile any sufficiently obsc
On Sun, 09 Jan 2005 22:12:13 -0500, William Ballard wrote:
> All:
>
> Some of you have probably seen my gripes about ndiswrapper-source.
> I moved on past all that -- but upstream is debianizing it and
> it's better in many ways.
>
> The alternate location is:
> http://ndiswrapper.sourceforge.ne
>
> And I still don't think anyone could argue that it would be reasonable
> to stick a driver on a Debian CD with a README that says "if you want
> to use this driver, you'll need to write a firmware file for your SCSI
> card. Use the following assembler"
>
I never said the USER HAS to wri
Hello,
I have just uploaded packages for teTeX-2.99.7, the first release
candidate of teTeX-3.0, into experimental. An upload of the more recent
rc2, 2.99.8, will follow in a couple of days. I would be glad if people
could test this.
Of special interest is whether packages Build-depending on
libk
On Mon, 2005-01-10 at 11:55 +1100, Sam Watkins wrote:
> On Sun, Jan 09, 2005 at 04:17:14PM -0500, Glenn Maynard wrote:
[snip]
> I ask people to please make a great effort to be polite and
> "professional" in representing Debian. Please don't tell newbies to go
> RTFM
Sure you should.
I remember,
Ron Johnson wrote:
> On Mon, 2005-01-10 at 11:55 +1100, Sam Watkins wrote:
>
>>On Sun, Jan 09, 2005 at 04:17:14PM -0500, Glenn Maynard wrote:
>
> [snip]
>
>>I ask people to please make a great effort to be polite and
>>"professional" in representing Debian. Please don't tell newbies to go
>>RTF
Hello.
I have a problem with the text (tty) terminals. The problem is that if I move
from the x-server to an tty text terminal I can't go back and I can't switch
to another tty terminal either. The only way to get back to X is to kill the
x-server.
This problem has arised since I deleted all
On Mon, Jan 10, 2005 at 03:45:56AM -0500, Andres Salomon wrote:
> Gee, the latest ndiswrapper has a bug. Downgrade to the one in
> testing, or upgrade to the one I uploaded today. It's not the
> end of the world. Perhaps you could even be helpful and let me
> know whether rc2 hangs in the same w
Hello,
I'm developing an application using libglib2.0-dev and automake 1.7. I'm
using AM_PATH_GLIB_2_0 macro in my configure.ac. In the default
installation, aclocal fails to find the macro unless I link
/usr/share/aclocal/glib-2.0.m4 to /usr/share/aclocal-1.7.
Is there a good way to build the pr
On Jan 10, 2005 at 14:31, William Ballard praised the llamas by saying:
> On Mon, Jan 10, 2005 at 03:45:56AM -0500, Andres Salomon wrote:
> > Gee, the latest ndiswrapper has a bug. Downgrade to the one in
> > testing, or upgrade to the one I uploaded today. It's not the
> > end of the world. Per
Hi,
I've uploaded a new version of the pcmcia-cs package to experimental,
3.2.8-2. This package has a lot of new features, including:
* Latest upstream version.
* Starts much earlier on boot, in the S runlevel.
* Doesn't ifup network cards, lets hotplug handle them instead.
* Detects some problem
On Mon, 2005-01-10 at 09:31 -0500, William Ballard wrote:
> On Mon, Jan 10, 2005 at 03:45:56AM -0500, Andres Salomon wrote:
> > Gee, the latest ndiswrapper has a bug. Downgrade to the one in
> > testing, or upgrade to the one I uploaded today. It's not the
> > end of the world. Perhaps you could
Le lun 2005-01-10 a 09:19:17 -0500, Bjorn Johansson <[EMAIL PROTECTED]> a dit:
>
> Hello.
>
> I have a problem with the text (tty) terminals. The problem is that if I move
> from the x-server to an tty text terminal I can't go back and I can't switch
> to another tty terminal either. The only w
Le dim 2005-01-09 a 14:20:10 -0500, Roberto Sanchez <[EMAIL PROTECTED]> a dit:
> Quoting "Simon Raven / Eric S. CÃÂtÃÂ" <[EMAIL PROTECTED]>:
>
>
> Thanks. Fixed. I seem to make that typo quite a bit. If you don't believe
> me you should see some of the bug's I've submitted to BTS. Apparently,
On Jan 10, 2005 at 15:08, Simon Raven / Eric S. Côté praised the llamas by
saying:
> Le lun 2005-01-10 a 09:19:17 -0500, Bjorn Johansson <[EMAIL PROTECTED]> a dit:
> >
> > Hello.
> >
> > I have a problem with the text (tty) terminals. The problem is that if I
> > move
> > from the x-server to
Hi all,
Occasionally, upgrading a Debian unstable (or testing) system results in
breakage. Sometimes the bugs are not immediately detected, or they are not
easily located to a single package, especially if the upgrade in question
contained many libraries or other shared code. Thus it would be usef
On Mon, 10 Jan 2005 14:57:48 +, David Pashley wrote:
[...]
> Unless I've got this very wrong, but the ndiswrapper source supplied in
> the SF deb is different to the source provided in the Debian package in
> the archive. This suggests it isn't down to the packaging.
You are correct; they are
On Mon, Jan 10, 2005 at 09:00:18AM -0600, Ron Johnson wrote:
> That's still no reason to rip the d-d.
I didn't rip it. I said I'm not griping -- just remarked on
the fact that the upstream is already Debianized and is not
broken.
I don't think the maintainer even uses ndiswrapper on his
system.
Baurjan Ismagulov wrote:
> I'm developing an application using libglib2.0-dev and automake 1.7. I'm
> using AM_PATH_GLIB_2_0 macro in my configure.ac. In the default
> installation, aclocal fails to find the macro unless I link
> /usr/share/aclocal/glib-2.0.m4 to /usr/share/aclocal-1.7.
Probably
Am Montag, 10. Januar 2005 17:06 schrieb Baurjan Ismagulov:
> Hello,
>
> I'm developing an application using libglib2.0-dev and automake
> 1.7. I'm using AM_PATH_GLIB_2_0 macro in my configure.ac. In the
> default installation, aclocal fails to find the macro unless I link
> /usr/share/aclocal/glib
On Mon, 2005-01-10 at 11:06 -0500, William Ballard wrote:
> On Mon, Jan 10, 2005 at 09:00:18AM -0600, Ron Johnson wrote:
> > That's still no reason to rip the d-d.
>
> I didn't rip it. I said I'm not griping -- just remarked on
> the fact that the upstream is already Debianized and is not
> broke
On Mon, 2005-01-10 at 15:03 +0100, Bjorn Johansson wrote:
[snip]
> This problem has arised since I deleted all files i /lib. Then I reinstalled
Deleted all files in /lib, eh?
--
-
Ron Johnson, Jr.
Jefferson, LA USA
PGP Key ID 8834C0
On Sun, Jan 09, 2005 at 10:12:13PM -0500, William Ballard wrote:
> All:
>
> Some of you have probably seen my gripes about ndiswrapper-source.
> I moved on past all that -- but upstream is debianizing it and
> it's better in many ways.
>
Frankly speaking, I see no reason to not simply bugging th
On Mon, Jan 10, 2005 at 10:15:06AM -0600, Ron Johnson wrote:
> "shove ... down everybody's throat"
> "You've F'd it up beyond all recognition"
I filed a bug nice and the guy closed it about 14 minutes later
immediately saying "there is no problem." The maintainer is dead-set on
following his ch
On Mon, Jan 10, 2005 at 05:21:53PM +0100, Francesco P. Lovergine wrote:
> identify problems, both in upstream and packaged versions. Posting in
> d-d is at least inappropriate.
It's an open list.
The problem is the upstream has the goal of producing a package that
works and another guy is trying
|| On Mon, 10 Jan 2005 17:42:17 +0200
|| Teemu Ikonen <[EMAIL PROTECTED]> wrote:
ti> I've been playing with putting the /etc directory plus a list of currently
ti> installed packages and their versions under version control. In principle,
ti> a "rollback" to any previous system state would be pos
On Jan 10, 2005 at 16:24, William Ballard praised the llamas by saying:
> On Mon, Jan 10, 2005 at 10:15:06AM -0600, Ron Johnson wrote:
> > "shove ... down everybody's throat"
> > "You've F'd it up beyond all recognition"
>
> I filed a bug nice and the guy closed it about 14 minutes later
> immedi
* William Ballard ([EMAIL PROTECTED]) [050110 17:35]:
> Listen, I'm just going to say this and not reply to all the bazillion
> other flames which are coming:
>
> The upstream is better. It's already Debianized. Do not use the one in
> the Debian archive.
I consider this as rude.
Cheers,
An
[Teemu Ikonen]
> Thus it would be useful to know what has changed in a past upgrade,
> or when a certain package was last upgraded. Unfortunately, apt and
> dpkg do not have built-in logging (see #134694).
I tell apt-listchanges to email me a list of changes on every upgrade,
and can thus use the
Hello all,
I've reached the end of my rope with this and I'm left scratching my head.
I'm hoping someone out there has more of a clue than I do.
I'm building a set of custom installation CDs for our network. The client
boots from a ramdisk image on the CD, loads modules, set up networking, and
On 10/01/05 14:32, Otavio Salvador wrote:
> || On Mon, 10 Jan 2005 17:42:17 +0200
> || Teemu Ikonen <[EMAIL PROTECTED]> wrote:
>
> ti> I've been playing with putting the /etc directory plus a list of currently
> ti> installed packages and their versions under version control. In principle,
> ti>
On Mon, Jan 10, 2005 at 06:44:14PM +0200, Teemu Ikonen wrote:
> Maybe (and probably) some packages modify their data (which is not part of
> the package) so that downgrade is not possible, but I'd guess this kind of
> packages are not that common.
Anything that is linked to libdb is your biggest p
On Sun, Jan 09, 2005 at 08:13:46PM +, Steve McIntyre wrote:
>Joerg Jaspert writes:
>>
>>Package: wnpp
>>Severity: normal
>>
>>Hi
>>
>>Unfortunately we dont have the time the package needs, so help is
>>needed. Ideally you should know a bit of C and of Debian Packaging. You
>>should also know cd
* Andreas Barth <[EMAIL PROTECTED]>:
> > The upstream is better. It's already Debianized. Do not use the one in
> > the Debian archive.
>
> I consider this as rude.
But it's true.
--
Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED]
Charite - Universitätsmedizin Berlin
|| On Mon, 10 Jan 2005 18:44:14 +0200
|| Teemu Ikonen <[EMAIL PROTECTED]> wrote:
ti> On 10/01/05 14:32, Otavio Salvador wrote:
>> || On Mon, 10 Jan 2005 17:42:17 +0200
>> || Teemu Ikonen <[EMAIL PROTECTED]> wrote:
>>
ti> I've been playing with putting the /etc directory plus a list of currently
This message has been generated automatically.
If you have sent an email with an attachment, please be sure that your intended recipient is aware. As a general policy, we immediately delete all emails with attachments that we are not expecting - even from known contacts and colleagues.
#include
* William Ballard [Mon, Jan 10 2005, 11:32:45AM]:
> On Mon, Jan 10, 2005 at 05:21:53PM +0100, Francesco P. Lovergine wrote:
> > identify problems, both in upstream and packaged versions. Posting in
> > d-d is at least inappropriate.
>
> It's an open list.
There is some reason for its ex
On Mon, Jan 10, 2005 at 06:14:05PM +0100, Eduard Bloch wrote:
> What are other packages?!
The other packages which depend on module-assistant.
> the module-assistant package (about 40kB) but provides some comfort for
> users and comfort, code size reduction, extendability, automatic feature
> upg
[Otavio Salvador]
> No because some applications doesn't depends only of configuration
> files but data-files. When you purge then, all data files will be
> removed together (in major of times). Another problem is how you can
> revert upgrade processes in database files and like?
RPM have a featur
Package: wnpp
Severity: wishlist
* Package name: libncar-graphics
Version : 4.4.0 and counting, quickly
Upstream Author : UCAR, C/O Mary Haley
* URL : http://ngwww.ucar.edu/ng/
* License : GPL2
Description : scientific visualization suite from UCAR
Graphi
Even if the d-d for ndiswrapper has done something wrong or not, even if
the upstream package is better (I don't know the facts, and I'm not
personally interested), it is NOT necessary to be rude and go on the
offensive like this. Please simply state your case, using calm language
and unadorned fa
On Mon, Jan 10, 2005 at 06:40:39PM +0100, Petter Reinholdtsen wrote:
> [Otavio Salvador]
> > No because some applications doesn't depends only of configuration
> > files but data-files. When you purge then, all data files will be
> > removed together (in major of times). Another problem is how you
101 - 147 of 147 matches
Mail list logo
