> > > Have you tried with the i386 version of chromium? It could be that
> > > it only affects i386 and not amd64.
> >
> > Quite possible, I can definitely reproduce it on i386.
>
> OK, I am bumping the severity again to prevent migration to testing
> for now.
Too late! It has already propagat
Package: upgrade-reports
Severity: important
Tags: wheezy
Upgrading 64-but squeeze to 64-bit wheezy on a AMD-64. /boot is (now)
on an ordinary partition, and / is on LVM on RAID.
I started with this upgrade from squeeze to wheezy a few weeks ago. It
has been only partially successful, and th
Well, the thought involved in writing the upgrade report was helpful.
It forced me to sit and think while waiting for a reply. Even without a
reply, that helped.
I did some more hacking. Of course I should have tried apt-get -f
install. That indeed fixed most of the problems. But didn't ge
That does look to be the problem., thanks.
It is a server I want, and the old server (dating back to etch, I have
no idea why the successive upgrades all the way to squeeze didn't
replace it) was configured at /etc/dhcpd.conf instead of
/etc/dhcp/dhcpd.conf. Probably a problem with a long-obsol
Yes, it looks like that was the problem with dhcp. I put a dhcpd.conf
in /etc/dhcp/ instead of /etc/, and it all works now.
That file should have been in the new place even in squeeze, so this is
definitely not a squeeze->wheezy upgrade problem. I was still using he
dhcp server from etch, in
I have no further issues with wheezy, except maybe the disappearance of
pornview, which was my preferred slide viewer (it doesn't actually
check whether the images are porn, so it works fine for landscapes and
such), but that's really a different issue.
But the old version from squeeze still wo
I'm in complte agreement with closing this bug. A few months later, I
upgraded from squeeze to wheezy successfully, and wheezy has been
running on my server ever since.
I submitted this bug report while wheezy was still in development, in
the hope that it would help debug the upgrade process.
On Mon, Nov 24, 2014 at 08:01:10AM +0100, Niels Thykier wrote:
> +It is generally advisable to purge removed packages. This is
> +especially true, if these have been removed in an earlier release
^
English does not use a comma here, though some other languages do.
>
The patch was to add the O_LARGEFILE option fo several I/O calls in
its core/adb/sysdeps.h file/
I find myself wondering why this fix hasn't even arrived in sid yet, as
far as I can tell.
It appears to be a serious bug, since it's possible that someone
might thingk he has performed a backup an
On Sat, Jul 11, 2015 at 10:16:15AM +0200, Nagel, Peter (IFP) wrote:
> The problem might be related to
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789152.
> However, in my case everything seems to be fine as long as all
> harddisks (within the RAID) are working.
> The Problem appears only if
On Thu, Jan 15, 2015 at 11:12:19AM +1100, Stuart Prescott wrote:
> Hi Niels,
>
> > +If needed be, it is possible to override the systemd unit file to
> > +have it start the sysvinit script. For more information on
> > +systemd unit files, please have a look at the following resources.
On Mon, Dec 15, 2014 at 05:00:32PM +0100, Svante Signell wrote:
> +It is also a good idea to install
> + sysvinit-core, sysvint and sysvinit-utils
Might you mean sysvinit instead of sysvint ?
> + as the first packages when upgrading.
-- hendrik
--
To UNSUBSCRIBE, email to debian-b
I hit this bug, read the previous messages, and wondered why it had
not been fixed in so long. I resolved to fix it myself, and spent
some time reading the code.
But then I was diverted to other tasks, and when I returned to the bug
a week later, it suddenly dawned on me why it was not a bug.
On Sun, Jan 29, 2023 at 09:39:41PM -0500, Antoine Beaupré wrote:
> On 2019-03-18 21:03:14, Paul Gevers wrote:
> > Hi Antoine,
> >
> > On 16-03-2019 15:46, Antoine Beaupré wrote:
> >> On 2019-03-16 15:18:27, Paul Gevers wrote:
> >>> On Mon, 05 Jan 2015 15:59:51 -0500 Antoine =?utf-8?Q?Beaupr=C3=A9?=
On Sun, Jan 02, 2011 at 07:11:11PM +0100, Julien Cristau wrote:
> +Note that some packages larger than 300,000,000 bytes (and any packages
> +depending on them) are excluded from the CD set. They are
> +still included in the DVD and Blu-ray disks, though.
maybe mention
and of course they can
On Sun, Jan 02, 2011 at 09:49:26PM +0100, Holger Wansing wrote:
> Package: release-notes
> Severity: wishlist
>
>
> Hello,
>
> I want to ask, if it would make sense to advice the user, to
> close any running X server when doing an dist-upgrade.
>
> Pro:
> you would reduce the risk of getting a
On Tue, Jan 04, 2011 at 07:42:00AM -0800, Steve Langasek wrote:
> On Tue, Jan 04, 2011 at 10:06:12AM +0100, Holger Wansing wrote:
> > ow...@bugs.debian.org (Debian Bug Tracking System) wrote:
> > > This is an automatic notification regarding your Bug report
> > > which was filed against the release
On Mon, Feb 07, 2011 at 08:48:39AM +0100, Javier Fernandez-Sanguino wrote:
> On 7 February 2011 07:27, Karl O. Pinc wrote:
> > During upgrade the text console was lost and replaced with a gdm login
> > screen. The second time this occurred neither the keyboard or mouse
> > would respond. Unplugg
By holding one key down all the time, all the other keys I type register
properlt. For example, while holding the 'a' key down with one hand,
I can easily type 'xterm' with the other. Then, of course, I can use xterm,
which does not have this problem.
THis may be why Greg Sharp has some succes
On Tue, Sep 07, 2021 at 06:54:05AM +0200, Joost van Baal-Ilić wrote:
> Hi,
>
> On Mon, Sep 06, 2021 at 05:23:45PM -0400, Hendrik Boom wrote:
> > On Mon, Sep 06, 2021 at 10:01:10PM +0100, Roger Lynn wrote:
> > > Package: release-notes
> > > Severity: important
On Thu, Sep 09, 2021 at 09:35:05PM +0200, Paul Gevers wrote:
> Hi Hendrik,
>
> On 09-09-2021 21:27, Hendrik Boom wrote:
> > Here is the text I have included in the current draft upgrade
> > instructions for Devuan:
> >
> > Warning: `wicd` will no longer be a
The example Pascal program in the original bug report is now
misclassified as Java source. This is on a new buster install as of
2019 01 19.
guest@buster:~$ file Downloads/emil23m.pas
Downloads/emil23m.pas: Java source, ASCII text
guest@buster:~$ file --version
file-5.35
magic file from /etc/m
Package: os-prober
Version: 1.77
os-prober fails to find any os's at all after a new Debian buster install,
not even the installed and running DEbian buster.
The install was done using the net-install CD on a USB stick on 2019 01 18,
downloaded immediately before the installation.
root@buster:/h
Just for comparison, on Devuan ascii (stretch wirhout systend), I get:
root@midwinter:/home/hendrik# os-prober
File descriptor 8 (socket:[13898]) leaked on lvs invocation. Parent PID 2831:
/bin/sh
File descriptor 9 (socket:[13899]) leaked on lvs invocation. Parent PID 2831:
/bin/sh
File descript
So the remaining problem is that the Debian Buster os-prober did not
recognise Devuan ascii.
-- hendrik
On Sun, May 03, 2020 at 09:34:34AM +0200, Niels Thykier wrote:
> Paul Gevers:
> > Dear Benedikt, all,
> >
> > On 16-04-2020 10:44, Benedikt Tuchen wrote:
> >> While doing an upgrade from Stretch to Buster on a Laptop with XFS
> >> Filesystem in use. After the upgrade the laptop doesn't boot into
>
26 matches
Mail list logo
