7le1Q-0003sT-00; Sun, 01 Sep 2002 16:20:48 -0700
Received: from chip by tytlal with local (Exim 3.35 #1 (Debian))
id 17le13-0007sH-00; Sun, 01 Sep 2002 19:20:25 -0400
From: [EMAIL PROTECTED]
Subject: dselect: dselect gets SIGSEGV on exit
To: [EMAIL PROTECTED]
X-Mailer: bug 3.3.10.1
Mess
13:56:39 -0700
Received: (from [EMAIL PROTECTED])
by caliban.lbl.gov (8.12.6/8.12.6/Debian-2) id g7VKud4J020394;
Sat, 31 Aug 2002 13:56:39 -0700
Date: Sat, 31 Aug 2002 13:56:39 -0700
Message-Id: <[EMAIL PROTECTED]>
From: Alex Romosan <[EMAIL PROTECTED]>
Subject: dse
Processing commands for [EMAIL PROTECTED]:
> tag 159233 + pending
Bug#159233: dselect: dselect gets SIGSEGV on exit
Tags added: pending
> merge 159233 159023
Bug#159023: dselect: dselect core dumps
Bug#159233: dselect: dselect gets SIGSEGV on exit
Bug#159212: dselect: dselect segfaults a
Processing commands for [EMAIL PROTECTED]:
> severity 159243 normal
Bug#159243: dselect segfaults on exit
Severity set to `normal'.
> tag 159243 pending
Bug#159243: dselect segfaults on exit
Tags added: pending
> merge 159243 159023
Bug#159023: dselect: dselect core dumps
Bug#1
severity 159243 normal
tag 159243 pending
merge 159243 159023
thanks
> I get a segfault everytime I exit dselect after performing any operation.
> The following backtrace is provided when dselect is run through gdb:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x4
tag 159233 + pending
merge 159233 159023
thanks
On Sun, 1 Sep 2002 [EMAIL PROTECTED] wrote:
> Whenever I quit dselect, it suffers a segmentation violation. But it
> seems to work fine otherwise.
Fixed in 1.10.6, which is sitting in incoming.
Package: dselect
Version: 1.10.5
Severity: important
I get a segfault everytime I exit dselect after performing any operation. The
following backtrace is provided when dselect is run through gdb:
Program received signal SIGSEGV, Segmentation fault.
0x401396c0 in free () from /lib/libc.so.6
Package: dselect
Version: 1.10.5
Severity: normal
Whenever I quit dselect, it suffers a segmentation violation. But it
seems to work fine otherwise.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux tytlal 2.4.19rc5aa1 #1 Fri Aug 2 16:06:17 EDT 2002 i686
unknown
Processing commands for [EMAIL PROTECTED]:
> severity 159212 normal
Bug#159212: dselect: dselect segfaults at exit
Severity set to `normal'.
> tag 159212 + pending
Bug#159212: dselect: dselect segfaults at exit
Tags added: pending
> merge 159212 159023
Bug#159023: dselect: dsel
severity 159212 normal
tag 159212 + pending
merge 159212 159023
thanks
On Sun, 1 Sep 2002, Michael Hummel wrote:
> Dselect says good-bye with a segmentation fault.
Fixed and uploaded as 1.10.6(sitting in incoming).
Package: dselect
Version: 1.10.5
Severity: important
Hi!
Dselect says good-bye with a segmentation fault.
Gdb says:
This GDB was configured as "i386-linux"...(no debugging symbols found)...
Core was generated by `dselect'.
Program terminated with signal 11, Segmentation fault.
On Sun, 1 Sep 2002, Fabian Fagerholm wrote:
> Attaching two files, select-select.strace and select-exit.strace. The first
> is an strace of dselect while choosing Select, accepting the setup, and then
> choosing Select again (resulting in a segfault). The second is the same
> except t
Package: dselect
Version: 1.10.5
Followup-For: Bug #159023
Attaching two files, select-select.strace and select-exit.strace. The first
is an strace of dselect while choosing Select, accepting the setup, and then
choosing Select again (resulting in a segfault). The second is the same
except the
Processing commands for [EMAIL PROTECTED]:
> tag 159023 + pending
Bug#159023: dselect: dselect core dumps
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
tag 159023 + pending
thanks
On Sat, 31 Aug 2002, Adam Heath wrote:
> On Sat, 31 Aug 2002, Alex Romosan wrote:
>
> > after going into select trying to exit dselect or trying to go back
> > to select causes dselect to core dump.
>
> Grr. The unstripped dselect does
On Sat, 31 Aug 2002, Alex Romosan wrote:
> after going into select trying to exit dselect or trying to go back
> to select causes dselect to core dump.
Grr. The unstripped dselect does *NOT* segfault, but the stripped one does.
Package: dselect
Version: 1.10.5
Severity: normal
after going into select trying to exit dselect or trying to go back
to select causes dselect to core dump.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux caliban 2.4.20-pre5 #94 Wed Aug 28 21:10:10 PDT 2002 i686
Processing commands for [EMAIL PROTECTED]:
> reassign 157093 dselect
Bug#157093: ncurses-base: xterm-mono is not useable as an xterm without colors
Bug reassigned from package `ncurses-base' to `dselect'.
> thanks
Stopping processing here.
Please contact me if you need assista
Package: dselect
Version: 1.10.4
Severity: minor
This line should probably be removed from the man page:
dselect doesn't handle Recommends: field very well.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux dragon 2.4.19 #2 Sat Aug 3 13:43:4
Package: dselect
Version: 1.10.4
Severity: normal
When I select a package (mesag-dev) providing a virtual package (libgl-dev)
which another package (xlibmesa-dev) already provides, dselect changes to
"recursive package listing", and lists as reasons for mesag-dev for appearing:
|
On Sat, 2002-08-10 at 21:59, Glenn McGrath wrote:
> If it could be done safely in one step then im sure we can all agree that
> it would be better aproach.
It can't. To split a package, you have to add a Depends: for one Debian
release. That's just how it works.
For example, the spamassassin m
On Sat, 10 Aug 2002 21:07:23 +0200 (CEST)
Santiago Vila <[EMAIL PROTECTED]> wrote:
> Glenn McGrath wrote:
> > I think we should be reduceing the number of required packages, not
> > increasing them.
>
> You should consider the current dpkg/dselect status in sarge a
es it drags in other stuff, it complicates things
> and will only make things harder in the future.
It's not increasing. It's staying the same. Get a clue.
> What was the point in seperating dpkg and dselect, i thought it was going
> to simplify things its not.
Er, in wood
Glenn McGrath wrote:
> I think we should be reduceing the number of required packages, not
> increasing them.
You should consider the current dpkg/dselect status in sarge as the
first step of a two-step process. The purpose of the split is to
increase (in the long run) the freedom of dpkg/d
On Sat, Aug 10, 2002 at 07:16:30AM +1000, Glenn McGrath wrote:
> I think we should be reduceing the number of required packages, not
> increasing them.
Isn't it great how everyone starts whining about things like this,
when there's nothing to be done, beyond what's being done?
It gets even more
o have a Depends
> (or in the dselect case case Pre-Depends) for one Debian release. Why
> is this a big deal, anyways? I don't personally use it, but it's not
> like dselect takes up an enormous amount of disk space.
>
I think we should be reduceing the number of require
Florent Rougon <[EMAIL PROTECTED]> wrote:
> Glenn McGrath <[EMAIL PROTECTED]> wrote:
>
> > > > What about aptitude? How long do we keep using dselect, anyway?
>
> [...]
>
> > Technically it shouldnt be a dependency, its a only a dependency to
> &
On Fri, 2002-08-09 at 13:08, Glenn McGrath wrote:
> I think it would be sad to see this problem go unresolved till sarge+1
Sorry, that's how splitting packages works. You have to have a Depends
(or in the dselect case case Pre-Depends) for one Debian release. Why
is this a big deal,
On Sat, Aug 10, 2002 at 03:08:14AM +1000, Glenn McGrath wrote:
> > > Technically it shouldnt be a dependency, its a only a dependency to
> > > protect stupid people.
> >
> > No. Someone can be using dselect to run a distribution upgrade and there
> > is a pos
On Fri, 9 Aug 2002 17:56:23 +0200
Josip Rodin <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 09, 2002 at 07:51:59PM +1000, Glenn McGrath wrote:
> > Technically it shouldnt be a dependency, its a only a dependency to
> > protect stupid people.
>
> No. Someone can be using ds
On Fri, Aug 09, 2002 at 07:51:59PM +1000, Glenn McGrath wrote:
> Technically it shouldnt be a dependency, its a only a dependency to
> protect stupid people.
No. Someone can be using dselect to run a distribution upgrade and there is
a possibility a random package will break it and leave th
Glenn McGrath <[EMAIL PROTECTED]> wrote:
> > > What about aptitude? How long do we keep using dselect, anyway?
[...]
> Technically it shouldnt be a dependency, its a only a dependency to
> protect stupid people.
>
> If users _want_ to remove it they should be able t
On 08 Aug 2002 22:24:10 +0200
Florent Rougon <[EMAIL PROTECTED]> wrote:
> Lex Spoon <[EMAIL PROTECTED]> wrote:
>
> > What about aptitude? How long do we keep using dselect, anyway?
>
> Lots if people like dselect a lot (including myself), it is maintained,
>
Previously Santiago Vila wrote:
> In sarge+1, most probably.
Indeed.
Wichert.
--
_
/[EMAIL PROTECTED] This space intentionally left occupied \
| [EMAIL PROTECTED]http://www.wiggy.net/ |
| 1024D/2FA3BC
On Thu, 8 Aug 2002 21:24:23 +0200
Hendrik Sattler <[EMAIL PROTECTED]> wrote:
> Am Donnerstag, 8. August 2002 20:44 schrieb Sean 'Shaleh' Perry:
> > On 08-Aug-2002 Hendrik Sattler wrote:
> > > with the latest change in testing, dselect is in its own package.
>
Your message dated Fri, 9 Aug 2002 03:38:16 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#151629: dselect help exit
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is no
On 08-Aug-2002 Florent Rougon wrote:
> Lex Spoon <[EMAIL PROTECTED]> wrote:
>
>> What about aptitude? How long do we keep using dselect, anyway?
>
> Lots if people like dselect a lot (including myself), it is maintained,
> so why do you want to remove it?
>
ind
Lex Spoon <[EMAIL PROTECTED]> wrote:
> What about aptitude? How long do we keep using dselect, anyway?
Lots if people like dselect a lot (including myself), it is maintained,
so why do you want to remove it?
> Also, isn't there some debian-base package around that everyone has
On Thu, Aug 08, 2002 at 09:54:41PM +0200, Santiago Vila wrote:
> Hendrik Sattler wrote:
> > Am Donnerstag, 8. August 2002 20:44 schrieb Sean 'Shaleh' Perry:
> > > On 08-Aug-2002 Hendrik Sattler wrote:
> > > > with the latest change in testing, dselect
Hendrik Sattler wrote:
> Am Donnerstag, 8. August 2002 20:44 schrieb Sean 'Shaleh' Perry:
> > On 08-Aug-2002 Hendrik Sattler wrote:
> > > with the latest change in testing, dselect is in its own package. But why
> > > does dpkg depends on that package?
Am Donnerstag, 8. August 2002 20:44 schrieb Sean 'Shaleh' Perry:
> On 08-Aug-2002 Hendrik Sattler wrote:
> > with the latest change in testing, dselect is in its own package. But why
> > does dpkg depends on that package? Isn't dselect just a frontend to dpkg?
>
Previously Sean 'Shaleh' Perry wrote:
> most likely so that dselect did not just silently disappear during the
> upgrade.
Indeed. Having dselect disappear in the middle of an upgrade using
dselect would be somewhat
On 08-Aug-2002 Hendrik Sattler wrote:
> Hi,
>
> with the latest change in testing, dselect is in its own package. But why
> does dpkg depends on that package? Isn't dselect just a frontend to dpkg? If
> yes, shouldn't then dselect depend on dpkg and not the other
Hi,
with the latest change in testing, dselect is in its own package. But why
does dpkg depends on that package? Isn't dselect just a frontend to dpkg? If
yes, shouldn't then dselect depend on dpkg and not the other way?
Thanks alot for clarification
HS
BTW: I am not subcribed to
Here's a possible clue. When I manage to get the help screen to display
without garbage while TERM=xterm-mono, I get this:
quit, exit, overwrite (note capitals!):
return confirm, quit (check dependencies)
q confirm, quit (override dep.s)
x, esc exit, abandoning any changes made
r
Package: dselect
Version: 1.10.4
Severity: normal
Long ago I discovered that I didn't like dselect's colors, and found
that they could easily be disabled by either using the -cm option of
xterm or setting TERM to xterm-mono.
That worked fine until recently. Now dselect sometimes
Processing commands for [EMAIL PROTECTED]:
> reassign 152591 dselect
Bug#152591: dpkg: dselect fails to update system: unable to access method
script...
Bug reassigned from package `dpkg' to `dselect'.
> severity 152591 important
Bug#152591: dpkg: dselect fails to update s
reassign 152591 dselect
severity 152591 important
tags 152591 pending
merge 152137 152591
thanks
Previously Martin Fluch wrote:
> [EMAIL PROTECTED]:~> dselect update
> dselect: unable to access method script `/usr/lib/dpkg/methods/disk/setup':
> No such file or directory
Let
Package: dpkg
Version: 1.10.2
Severity: normal
I get the following error since a couble of days:
[EMAIL PROTECTED]:~> dselect update
dselect: unable to access method script `/usr/lib/dpkg/methods/disk/setup': No
such file or directory
The same happens when I issue the command: dselec
Processing commands for [EMAIL PROTECTED]:
> tag 152323 + pending
Bug#152323: dselect bonks out on [A]ccess, [U]pdate menu choices
Bug#152137: dpkg misses /usr/lib/dpkg/methods/disk/setup, breaks dselect
Bug#152161: dselect cannot update because /usr/lib/dpkg/methods/disk/setup
Bug#152
Processing commands for [EMAIL PROTECTED]:
> tag 152372 + pending
Bug#152372: wajig: Update failed
Tags added: pending
> merge 152372 152137
Bug#152137: dpkg misses /usr/lib/dpkg/methods/disk/setup, breaks dselect
Bug#152372: wajig: Update failed
Bug#152161: dselect cannot update becaus
tag 152372 + pending
merge 152372 152137
thanks
On Tue, 9 Jul 2002, Tim Mattison wrote:
> Backing up the directory /usr/lib/dpkg/methods/disk and restoring it
> after you receive the error message:
>
> dselect: unable to access method script
> `/usr/lib/dpkg/methods/disk/setup&#x
Processing commands for [EMAIL PROTECTED]:
> severity 152370 important
Bug#152370: dpkg: dselect fails on upgrade: dpkg to blame?
Severity set to `important'.
> reassign 152370 dselect
Bug#152370: dpkg: dselect fails on upgrade: dpkg to blame?
Bug reassigned from package `dpkg&#
severity 152323 important
merge 152323 152137
thanks
On Mon, 8 Jul 2002, Steve VanDevender wrote:
> Choosing the [A]ccess or [U]pdate items in the main menu of 'dselect'
> results in the error message:
>
> dselect: unable to access method script`/usr/lib/dpkg/methods/disk/s
severity 152370 important
reassign 152370 dselect
merge 152370 152137
tag 152370 + pending
thanks
On Tue, 9 Jul 2002, nick wrote:
> After upgrading to dpkg 1.10.2, running update from within
> dselect results in an error:
>
> dselect: unable to access method script `/usr/lib/dpkg/
Processing commands for [EMAIL PROTECTED]:
> severity 152323 important
Bug#152323: dselect bonks out on [A]ccess, [U]pdate menu choices
Severity set to `important'.
> merge 152323 152137
Bug#152137: dpkg misses /usr/lib/dpkg/methods/disk/setup, breaks dselect
Bug#152323: dselect bonk
Package: dselect
Version: 1.10.2
Followup-For: Bug #152372
-- System Information:
Debian Release: 3.0
Architecture: i386
Kernel: Linux neutrino 2.4.17 #56 Sun Jul 7 04:15:22 EDT 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages dselect depends on:
ii libc62.2.5-7
Package: dpkg
Version: 1.10.2
Severity: grave
Tags: sid
Justification: renders package unusable
After upgrading to dpkg 1.10.2, running update from within
dselect results in an error:
dselect: unable to access method script `/usr/lib/dpkg/methods/disk/setup': No
such file or dire
Package: dselect
Version: 1.10.2
Choosing the [A]ccess or [U]pdate items in the main menu of 'dselect'
results in the error message:
dselect: unable to access method script`/usr/lib/dpkg/methods/disk/setup': No
such file or directory
and an immediate exit from 'dselect'
tags 152276 pending
severity 152276 important
merge 152276 152137
thanks
Previously Dave Carrigan wrote:
> I ran dselect this morning, and when I choose the update option, dselect
> exits with the error:
Known problem, already reported 4 times.
W
Processing commands for [EMAIL PROTECTED]:
> tags 152276 pending
Bug#152276: Dselect dies with "unable to access method script" message
Tags added: pending
> severity 152276 important
Bug#152276: Dselect dies with "unable to access method script" message
Severity se
Package: dselect
Version: 1.10.2
Severity: grave
I ran dselect this morning, and when I choose the update option, dselect
exits with the error:
dselect: unable to access method script `/usr/lib/dpkg/methods/disk/setup': No
such file or directory
That directory is empty other than a names
Your message dated Mon, 8 Jul 2002 16:06:21 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#152269: dselect is not optional, but aptitude thinks it is
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If t
On Mon, Jul 08, 2002 at 10:12:43PM +0900, Stephen J. Turnbull wrote:
> Package: dpkg
> Version: 1.10
>
> Trying to upgrade dpkg (to 1.10.2) resulted in a broken dependency
> because I had removed the dselect package. I suppose this is
> something in the dpkg dependencies, thus
Package: dpkg
Version: 1.10
Trying to upgrade dpkg (to 1.10.2) resulted in a broken dependency
because I had removed the dselect package. I suppose this is
something in the dpkg dependencies, thus the report against dpkg.
In aptitude simply reselecting dselect resulted in a smooth upgrade
Processing commands for [EMAIL PROTECTED]:
> severity 152231 important
Bug#152231: dselect: dselect update horribly broken!
Severity set to `important'.
> tags 152231 pending
Bug#152231: dselect: dselect update horribly broken!
Tags added: pending
> merge 152137 152231
Bug#15213
other methods to install those. Also
sid doesn't get security updates anyway so the point is moot.
Finally, is it really that hard to check if perhaps someone else already
filed this bugreport? A 10-second check on
http://bugs.debian.org/dselect would have told you that two people
already sub
retitle 152231 dselect: dselect update horribly broken!
thanks
s/dselect select/dselect update/g
(Corrected) transcript follows.
# dselect update
dselect: unable to access method script
`/usr/lib/dpkg/methods/disk/setup': No such file or
+directory
# ls -l /usr/lib/dpkg/methods/disk/
to
Processing commands for [EMAIL PROTECTED]:
> retitle 152231 dselect: dselect update horribly broken!
Bug#152231: dselect: dselect select horribly broken!
Changed Bug title.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system adminis
Package: dselect
Version: 1.10.2
Severity: grave
2) Important Bug. Has a major effect on the usability of a package,
without rendering it completely unusable to everyone.
More than that, since it's now unusable.
4) Critical bug. Makes unrelated software on the syste
reassign 152137 dselect
severity 152137 important
thanks
On Sun, 7 Jul 2002, Rüdiger Kuhlmann wrote:
>
> Package: dpkg
> Version: 1.10.2
> Severity: grave
>
> (grave because it renders dselect unusable)
This is not a dpkg bug, but a dselect bug. And, because it
Package: dselect
Version: 1.10.2
Severity: important
Tags: sid
I would say this bug is important to grave because it isn't possible to
update witch dselect which is a very base tool on debian.
The error message is:
dselect: unable to access method script
`/usr/lib/dpkg/methods/disk/setup
Package: dpkg
Version: 1.10.2
Severity: grave
(grave because it renders dselect unusable)
| [EMAIL PROTECTED]:/usr/local/debs# LANG=C LC_ALL=C
| [EMAIL PROTECTED]:/usr/local/debs# dpkg -S /usr/lib/dpkg/methods/disk/setup
| dpkg: /usr/lib/dpkg/methods/disk/setup not found.
| [EMAIL PROTECTED
severity 152132 minor
tags 152132 pending
thanks
Previously Lazarus Long wrote:
> Why put the man page for the file in a separate package from the file
> itself or from that which it configures?
It's called a bug.
> Move the latter two files to the dselect pacakge.
You know, a
Processing commands for [EMAIL PROTECTED]:
> severity 152132 minor
Bug#152132: dselect: dselect.cfg(5) is not in dselect package
Severity set to `minor'.
> tags 152132 pending
Bug#152132: dselect: dselect.cfg(5) is not in dselect package
Tags added: pending
> thanks
Stopping p
Package: dselect
Version: 1.10.2
Severity: normal
$ dlocate dselect.cfg
dselect: /etc/dpkg/dselect.cfg
dpkg: /usr/share/man/man5/dselect.cfg.5.gz
dpkg: /usr/share/man/sv/man5/dselect.cfg.5.gz
Why put the man page for the file in a separate package from the file
itself or from that which it
reassign 151727 apt
thanks
On Tue, 2 Jul 2002, Dan Jacobson wrote:
> Package: dpkg
> Version: 1.9.20
> Severity: important
>
> in dselct, choosing the apt-get method, we are faced with
>Do you wish to change (overwrite) it?[y/N]
> regarding our sources.list file.
>
> Well, already twice in th
Processing commands for [EMAIL PROTECTED]:
> reassign 151727 apt
Bug#151727: dpkg: dselect message " Do you wish to change (overwrite) it?[y/N]"
hazardous
Bug reassigned from package `dpkg' to `apt'.
> thanks
Stopping processing here.
Please contact me if you ne
Package: dpkg
Version: 1.9.20
Severity: important
in dselct, choosing the apt-get method, we are faced with
Do you wish to change (overwrite) it?[y/N]
regarding our sources.list file.
Well, already twice in the last month I have been shocked that my
sources.list was blown away by saying "y".
Processing commands for [EMAIL PROTECTED]:
> retitle 65318 cdrom method doesn't work if cdrom is mounted
Bug#65318: dpkg: cdrom: problem with mounted and not mounted cdrom
Changed Bug title.
> reassign 65318 dselect
Bug#65318: cdrom method doesn't work if cdrom is mounted
Bug
Package: dselect
Version: 1.10
Severity: grave
Example:
libpisock4 is obsolete. It is currently marked as held '='.
I select '_' to remove it.
The conflict resolution window appears, telling me that
gnome-pilot-conduits and gnome-pilot depend on libpisock4
and i
On Tue, Jul 02, 2002 at 01:30:30AM +, Lazarus Long wrote:
> Package: dselect
> While the stupid lack-of-appropriate-response to the spacebar upon
> invocation doesn't make the package completely unusable, it does at
> least make it significantly less likely that the new
On Mon, 1 Jul 2002, Glenn McGrath wrote:
> dselect was previously installed by the dpkg package, as dselect is now in
> its own package you can remove the dselect package, previously you
> couldnt.
Er, this is not right.
The dselect program used to be part of the dpkg package. Dpkg
Package: dselect
Version: N/A
Severity: important
2) Important Bug. Has a major effect on the usability of a package,
without rendering it completely unusable to everyone.
While the stupid lack-of-appropriate-response to the spacebar upon
invocation doesn't make the pa
ong with the old way,
>
> For example, that it was out of synch with the rest of programs that use
> scrolling on Unix? :)
Well, yes, I was aware of that. It's just annoying to change old habits. But
I just noticed that dselect has an --expert option which turns off the help
messages
Package: dselect
Version: 1.10
Severity: minor
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux huron 2.4.18-xfs-1.1 #1 Sat Apr 20 02:09:31 CEST 2002 i586
Locale: LANG=C, LC_CTYPE=C
Versions of packages dselect depends on:
ii libc62.2.5-7
Processing commands for [EMAIL PROTECTED]:
> reassign 11611 dselect
Bug#11611: /usr/lib/dpkg/methods/disk/setup needs updating
Bug reassigned from package `dpkg' to `dselect'.
> reassign 21400 dselect
Bug#21400: /usr/lib/dpkg/methods/disk/setup outputs junk
Bug reassigned from p
Processing commands for [EMAIL PROTECTED]:
> reassign 2834 dselect
Bug#2834: dselect loses state if it can't find a pre-dependency
Bug reassigned from package `dpkg' to `dselect'.
> retitle 7056 dselect nfs method does no package ordering
Bug#7056: dpkg 1.4.0.7 : prob
Processing commands for [EMAIL PROTECTED]:
> close 151531
Bug#151531: dselect: not properly UTF-8 ready
Bug closed, send any further explanations to Michael Piefel <[EMAIL PROTECTED]>
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tra
Processing commands for [EMAIL PROTECTED]:
> reopen 151531
Bug#151531: dselect: not properly UTF-8 ready
Bug reopened, originator not changed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debia
On Sun, Jun 30, 2002 at 05:52:43PM -0400, David Kamholz wrote:
> Package: dselect
> Version: 1.10
> Severity: minor
>
> I am used to typing space to dismiss the help screens dselect brings up.
> In version 1.10, this scrolls through the help -- it is now required to
> hit
Your message dated Mon, 1 Jul 2002 12:10:07 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#151531: dselect: not properly UTF-8 ready
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the c
Package: dselect
Version: 1.10
Severity: wishlist
Tags: patch
I spent some time on IRC today talking to a user who had messed up his
selections very badly in dselect and who had then mistakenly hit Enter.
Having done so, he was having great difficulty getting back to a sane
state: what he really
Package: dselect
Version: 1.10
Severity: minor
dselect incorrectly assumes that one byte in a string occupies one
column on the screen. This is used in dselect's main menu to align the
explanations of the 7 options. However, with UTF-8, this assumption may
not be true. For instance, the G
Your message dated Mon, 1 Jul 2002 09:30:22 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#151501: dpkg: dpkg depends on dselect
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
On Mon, 1 Jul 2002 13:23:47 +1000
Glenn McGrath <[EMAIL PROTECTED]> wrote:
> dselect was previously installed by the dpkg package, as dselect is now in
> its own package you can remove the dselect package, previously you
> couldnt.
Hmm.. debootstrap broke again?
I'm too busy
dselect was previously installed by the dpkg package, as dselect is now in
its own package you can remove the dselect package, previously you
couldnt.
Glenn
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: dpkg
Version: 1.9.21
Severity: normal
The latest upgrade of dpkg triggered the installation of dselect. Is this
absolutely necessary? I would really prefer not to have this package around
eating space.
-- System Information
Debian Release: 3.0
Kernel Version: Linux arrakis 2.4.17 #5 Sat
Package: dselect
Version: 1.10
Severity: minor
I am used to typing space to dismiss the help screens dselect brings up.
In version 1.10, this scrolls through the help -- it is now required to
hit enter to dismiss the screens. I see no particular reason to force
everyone to get used to a new
nux 2.4.4 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: dselect exits on window resize
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
Package: dpkg
Version: 1.9.6
Hi folks,
If I start dselect in an xterm an
201 - 300 of 588 matches
Mail list logo
