On Sat, Dec 07, 2024 at 03:44:43PM -0600, Steve M. Robbins wrote:
> Package: zfs-dkms
> Version: 2.2.6-2
> Severity: important
> Tags: upstream
>
> [...] I suspect an upstream fix is required.
Yes, this is quite common with zfs (and other out-of-tree kernel
modules, e.g. the proprietary nvidia dr
reopen 1020290
severity 1020290 critical
stop
There's no need to repeat (again!) what i've already said.
fix the bug before closing this report.
's not my responsibility to figure out what broken interactions your broken
package has with usrmerge, usr-is-merged, and apt itself. IT'S YOUR PACKAGE,
YOUR RESPONSIBILTY.
craig
--
craig sanders
On Wed, Sep 21, 2022 at 08:32:53AM +0200, Helmut Grohne wrote:
> On Wed, Sep 21, 2022 at 10:41:18AM +1000, Craig Sanders wrote:
> > Stop closing this bug without fixing it.
>
> The change you are objecting to was planned and presented to various
> teams in Debian including the t
reopen 1020290
severity 1020290 critical
stop
> Given you have made usrmerge uninstallable in your system as you
> admitted (probably running one of dpkg's unsupported scripts that
> installs a local blocking package, I'd imagine) then it is entirely on
> you to fix that, it cannot be done remotel
70 or anything
similar, or to anything even related to nvidia. Here's it's debian/control
file:
$ cat debian/control
Source: dlocate
Section: utils
Priority: optional
Maintainer: Craig Sanders
Standards-Version: 3.7.2.1
Build-Depends: debhelper (>= 13)
Package: dlocate
Architecture: all
De
administration easier. they're not a substitute for it.
craig
ps: this bug is an example of why testing is actually worse than sid for
real-world (non-testing) usage. This bug report, while necessary, actually
delayed the migration of the updated zfs packages that would have resolved
it. That&#
ke some minimal effort to document the changes.
thanks,
craig
--
craig sanders
quot;xf86EnableIOPorts: failed to set IOPL for
I/O (Operation not permitted)" error message in startx.log - and
so far google has been absolutely useless in revealing what that's
about...several people have complained about it but no-one has come up
with a definitive reason for it.
craig
--
craig sanders
x27;s a good and
clearly defined reason for it.
craig
--
craig sanders
Package: xinit
Version: 1.3.4-3
Severity: grave
Justification: renders package unusable
sometime in the last ~70 days (since I last started X or rebooted),
something has changed in X that prevents startx from working as an
ordinary user.
startx *was* working perfectly. Now when I run startx, I c
ority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl
pt pt-BR ru sv tr zh-CN zh-TW
#
# ForceLanguagePriority allows you to serve a result page rather than
# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# [in case no accepted languages matched the availab
.31 without
causing problems, but it seems an odd conflict to have.
'aptitude why-not nvidia-glx' says that that is the problem (it's wrong,
the problem is the missing dependancy xorg-video-abi-8.0).
# aptitude why-not nvidia-glx
ih nvidia-glx Conflicts nvidia-glx
--
craig san
k from removing pysol).
or both...there's probably no reason why pysol and pysolfc can't
co-exist if them gameplay differs substantially.
BTW, there are also updated card sets in PySolFC-Cardsets v.2.0.
craig
--
craig sanders
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ..
g a deal to be running
with an older version.
> (As an aside: NMUs that are new upstream versions should be versioned
> like 2.15a-0.1 to indicate that they're NMUs.)
and i'll change the version number to 2.15a-0.2
craig
--
craig sanders
--
To UNSUBSCRIBE, email
d."
please revert this change, or at least provide an equivalent alternative.
you can't just take away useful - even vital - functionality like this
without warning.
flagged as critical because of the security problems this causes.
craig
--
craig sanders
--
To UNSUBSCRIBE, e
On Sun, Aug 23, 2009 at 06:00:11PM -0600, LaMont Jones wrote:
> On Mon, Aug 24, 2009 at 07:47:59AM +1000, Craig Sanders wrote:
> > i'm talking about a network being disrupted, not a single host. the
> > hosts DON'T have 127.0.0.1 in resolv.conf, they have the namesever.
tual problems that have been described (and
experienced) when the name-server is killed early and started later.
a real-world, factual problem that actually happens beats a
hypothetical, never-yet-been-demonstrated problem every time.
craig
--
craig sanders
--
To UNSUBSCRIBE, email to d
e has worked reliably for many years with a restart
after upgrade rather than stop-early, start-late approach. there is no
reason for the current change in behaviour. it just maximises downtime.
craig
--
craig sanders
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Fri, Aug 21, 2009 at 10:35:13PM -0600, LaMont Jones wrote:
> On Sat, Aug 22, 2009 at 10:47:16AM +1000, Craig Sanders wrote:
> > when upgrading bind9, named is stopped until the upgrade is completed.
>
> And there is no real way to make sure it stays working while the
> libr
Package: bind9
Version: 1:9.6.1.dfsg.P1-3
Severity: critical
Justification: breaks unrelated software
when upgrading bind9, named is stopped until the upgrade is completed.
this could be a LONG time during an apt-get {dist-,dselect-,}upgrade,
especially if there are many packaged being upgraded
On Fri, Oct 10, 2008 at 08:23:26AM +0200, Rene Engelhard wrote:
> Already reported a few times and pending. What if you would look in the BTS
> first
> before filing the fifth instance of this?
i did look. didn't see anything resembling it, so submitted a bug report.
craig
--
tic. dh_installinit should do the right thing for the
general, most common, case and still allow manual overrides/workarounds
for special cases.
instead, it currently does the wrong thing for the general case,
handles the exception as if it is the rule, and requires manual
overrides/workarounds
On Tue, Mar 18, 2008 at 04:01:05AM +0100, Michael Biebl wrote:
> Craig Sanders wrote:
> > On Sun, Mar 16, 2008 at 03:14:58AM +0100, Michael Biebl wrote:
>
> > > Second, if you replace files while the daemon is still running,
> > > this can lead to all sorts of subt
their
daemon package having such problems. if there was a risk, then stop in
prerm, start in postinst. otherwise, just restart in the postinst.
in any case, it's only necessary for those daemon packages where there
IS such a problem or risk - it's not at all necessary for most daemon
ality trumps imagination.
craig
--
craig sanders <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sun, Mar 16, 2008 at 03:14:58AM +0100, Michael Biebl wrote:
> Craig Sanders wrote:
> > On Sun, Mar 16, 2008 at 01:16:22AM +0100, Michael Biebl wrote:
>
> >
> >>>> One of the reasons, why it is done this way, ist that you can't
> >>>> gu
On Sun, Mar 16, 2008 at 03:00:49AM +0100, Michael Biebl wrote:
> Craig Sanders wrote:
> > On Sun, Mar 16, 2008 at 01:16:22AM +0100, Michael Biebl wrote:
>
> >
> >> grep "invoke-rc.d .* stop" *.prerm
> >
> > 1. the fact that some other packages
On Sun, Mar 16, 2008 at 01:16:22AM +0100, Michael Biebl wrote:
> Craig Sanders wrote:
> > severity 471051 critical
> > thanks
> >
> > this bug can not be downgraded to normal because it is a bug that
> > results in a loss of important and irreplacable data
Package: debhelper
Version: 6.0.8
Severity: critical
Justification: causes serious data loss
dh_installinit adds code to a package's .prerm script to stop the daemon
at the beginning of the upgrade, and then adds code to restart it in the
.postinst script.
this results in important system daemon
Package: rsyslog
Version: 2.0.3-1
Severity: critical
Justification: causes serious data loss
rsyslog shuts down at the start of the upgrade and only gets restarted
when the package is configured.
this is broken. instead of stopping rsyslog in the prerm and starting it
in the postinst, just resta
kage having the tag "fixed", but
> were never closed.
hmmm. i guess i've just assumed all along that Fixed is equivalent to
Closed, and they don't actually need to be closed. i've adopted all the
NMU changes, so i'll just close all the Fixed bugs next time i upload an
update.
craig
--
craig sanders <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting
# uname -a
Linux ganesh.taz.net.au 2.6.20.14 #1 SMP PREEMPT Sun Jul 1 10:09:39 EST 2007
i686 GNU/Linux
# cat /proc/version
Linux version 2.6.20.14 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070601
(prerelease) (Debia
.20 and nvidia 100.14.19. no problems at all (just over 9 hours).
so far, the common factor in crashing machines seems to be the nvidia
7300 GS chipset combined with nvidia drivers 100.14.11 or 100.14.19.
craig
--
craig sanders <[EMAIL PROTECTED]>
"The fundamentalists deny that ev
34 matches
Mail list logo
