;Should bugs make it into Debian releases"?
> >
> > Ah, sorry, I think I misunderstood - you are literally asking if the
> > presence of a severity "serious" bug in Grub should have prevented
> > the whole 11.5 point release happening?
> >
> > I don't know
literally asking if the
presence of a severity "serious" bug in Grub should have prevented
the whole 11.5 point release happening?
I don't know. The only documentation I can find on the matter is
about full Debian releases and even that says the bugs would have to
be apmrked "releas
ce of a severity "serious" bug in Grub should have prevented
the whole 11.5 point release happening?
I don't know. The only documentation I can find on the matter is
about full Debian releases and even that says the bugs would have to
be apmrked "release-critical" (RC) to block rele
On Sun, Sep 11, 2022 at 09:23:17PM +0100, Tim Woodall wrote:
> Should https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 have
> made it into debian 11.5? I thought serious bugs shouldn't make it into
> stable?
I'm trying to read your email charitably in the sense that you are
wond
On Mon 12 Sep 2022 at 03:36:46 (+0100), Tim Woodall wrote:
> On Sun, 11 Sep 2022, Greg Wooledge wrote:
> > On Sun, Sep 11, 2022 at 09:23:17PM +0100, Tim Woodall wrote:
> > > Should https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 have
> > > made it into debian 1
On Sun, 11 Sep 2022, Greg Wooledge wrote:
On Sun, Sep 11, 2022 at 09:23:17PM +0100, Tim Woodall wrote:
Should https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 have
made it into debian 11.5? I thought serious bugs shouldn't make it into
stable?
Bugs have to be discovered and reported
On Sun, Sep 11, 2022 at 09:23:17PM +0100, Tim Woodall wrote:
> Should https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 have
> made it into debian 11.5? I thought serious bugs shouldn't make it into
> stable?
Bugs have to be discovered and reported. If nobody found th
Should https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017944 have
made it into debian 11.5? I thought serious bugs shouldn't make it into
stable?
I'm not sure this should be merely serious, it broke absolutely
everything for me and took me a while to track down.
Although the 'fix' was just
-5) 11.3.0, GNU
ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC
Debian 5.18.16-1 (2022-08-10)
The kernel running is from backports, I assume.
Kernels from backports may function different than release packages. You
can test whether it is a kerl bug or not, with installing
On 9/10/22 19:46, Maximiliano Estudies wrote:
Hi,
I seem to have hit a bug with the wireless card driver of my laptop.
This happened twice already, my laptop became unresponsive and I
couldn't issue any sudo commands. After hard rebooting the laptop I
see this entries in the syslog:
Sep 10 14
Hi,
I seem to have hit a bug with the wireless card driver of my laptop.
This happened twice already, my laptop became unresponsive and I
couldn't issue any sudo commands. After hard rebooting the laptop I
see this entries in the syslog:
Sep 10 14:51:50 user-thinkpad kernel: mt7921e :03:00.0
On Thu, Sep 08, 2022 at 06:22:47PM -0400, José Eduardo Niño wrote:
> Hola. Soy José Niño.
Hola, José
esta lista comunica en inglés. Por consecuencia, la mayoría aquí
no podrá ayudarte.
En caso que prefieras comunicar en castellano: hay una lista en
castellano por aquí:
Hola. Soy José Niño.
Tengo un problema particular con el hardware de mi computadora,
específicamente con la ranura lectora de memorias SD y microSD.
Con Debian 11.0 funciona perfectamente. Pero, al actualizar con apt upgrade
comienza a fallar.
Con Debian 11.4, al insertar la memoria SD en la
address by inserting
a space after the @ in the debian-user address.
I forgot about that, clicked send, and the email actually got sent, but the
From: was shown as "Undisclosed recipients".
I don't know whether I should consider that a bug or a feature ;-) But I'll
disable email addresses some
> On Aug 30, 2022, at 1:40 PM, Nicholas Geovanis wrote:
>
> When you run check_dns by hand on Host B, you don't say who you are logged-in
> as. That can make a difference. Nagios runs its scripts in a known
> environment which may be different than you expect.
>
Thanks for the question. I
On Tue, Aug 30, 2022, 2:13 PM Casey Deccio wrote:
> Hi all,
>
> I am having trouble tracking down a bug in my monitoring setup. It all
> happened when I upgraded the monitored host (host B in my example below) to
> bullseye. Note that Host A is also running bullseye, but the p
Hi all,
I am having trouble tracking down a bug in my monitoring setup. It all
happened when I upgraded the monitored host (host B in my example below) to
bullseye. Note that Host A is also running bullseye, but the problem didn't
show itself until Host B was upgraded.
Here is the setup
El 2022-08-30 a las 13:40 +0200, Sysadmin atlanTTic escribió:
Buf... no veo nada.
Todo el cuerpo del correo está en formato multipart/mixed y ni el
mailcap de Mutt lo puede reconocer.
> He intentado encontrar una solución sobre este bug de Debianhref="ma
<<< text/html; charset=UTF-8: Unrecognized >>>
OpenPGP_0xE27B2F86F273016E.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
On 05/08/2022 00:35, Mid Mes Fair wrote:
There is a big bug in auto update in debian 11.
I have turned off the auto checking feature but it still checking and
appear on the notification section in the software
ok.
--
With kindest regards, Piotr.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal
On Thu, Aug 4, 2022 at 7:51 PM Mid Mes Fair wrote:
> There is a big bug in auto update in debian 11.
> I have turned off the auto checking feature but it still checking and
> appear on the notification section in the software
>
We need more info. To start with:
What Desktop Environ
Richmond writes:
> This bug:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895378
>
> sky2: sky2: did not recover correctly after waking up from S3
>
> seems to be fixed on Ubuntu here:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921
>
&g
Hi list,
I've been having a problem with reading local email (like Cron reports
etc.) and I tracked it down to either Evolution or WebKitWebProcess.
I've opened bugs with both and have been talking with the Evolution
mailing list. Milan Crha from that list had me run some backtraces and
all he can
Hi,
Description of problem:
After suspend only one screen activates (dual screen system) and the mouse
seems to be unresponsive.
Basic System
Using AMD cards (Radeon 5600XT and 5500XTY)
My system is setup as a mult-seat system with one seat having two monitors
and the other with one monitor.
Anders Andersson (12022-05-04):
> On this note, I've always found it annoying that debian (and likely
> others) don't put /sbin in the normal user's $PATH. A lot of the tools
> there have uses other than modifying the system.
I have to unpack Zip files rather often, I use unzip in command-line.
On Wed, May 04, 2022 at 07:04:52AM -0600, Charles Curley wrote:
> On Wed, 4 May 2022 05:23:31 +0200
> Anders Andersson wrote:
>
> > On this note, I've always found it annoying that debian (and likely
> > others) don't put /sbin in the normal user's $PATH. A lot of the tools
> > there have uses
On Wed, 4 May 2022 05:23:31 +0200
Anders Andersson wrote:
> On this note, I've always found it annoying that debian (and likely
> others) don't put /sbin in the normal user's $PATH. A lot of the tools
> there have uses other than modifying the system.
It can be annoying, but for good reason. In
On Wed, May 04, 2022 at 05:23:31AM +0200, Anders Andersson wrote:
[on sbin]
> On this note, I've always found it annoying that debian (and likely
> others) don't put /sbin in the normal user's $PATH. A lot of the tools
> there have uses other than modifying the system.
I've grown accustomed to
On Mon, May 2, 2022 at 8:19 PM wrote:
> On Mon, May 02, 2022 at 07:58:12PM +0200, Michael Lange wrote:
> > On Mon, 2 May 2022 10:17:06 -0500
> > Richard Owlett wrote:
> > > I'm using Debian 10.7 with MATE DE [will be updated later this week]
> > > The machine is a Lenovo T510 and is setup to
On Mon, May 02, 2022 at 07:58:12PM +0200, Michael Lange wrote:
> Hi,
>
> On Mon, 2 May 2022 10:17:06 -0500
> Richard Owlett wrote:
>
> > I'm using Debian 10.7 with MATE DE [will be updated later this week]
> > The machine is a Lenovo T510 and is setup to login as either "richard"
> > or
Hi,
On Mon, 2 May 2022 10:17:06 -0500
Richard Owlett wrote:
> I'm using Debian 10.7 with MATE DE [will be updated later this week]
> The machine is a Lenovo T510 and is setup to login as either "richard"
> or "root".
>
> If logged in as "richard" I can execute su {+ password} and receive a
>
decides where it's going to write it,
> ie which block group. Only then does it create the file's inode,
> so that it can keep file contents and inode close together.
That actually makes sense. It would be surprising behaviour,
but at least whithin reach; whether it's intentional or may be
considere
On Mon, May 02, 2022 at 03:43:41PM +, Andrew M.A. Cater wrote:
> Not bug - feature.
I disagree. Strongly. It is a CHANGE, but it is not a feature.
> See also su -
>
> It's in the release notes, I'm fairly sure.
It's also at <https://wiki.debian.org/NewInBuster#Changes>.
ot; I can execute su {+ password} and receive a prompt
> indicating I'm "root".
>
> However if I then enter "update-grub", the response is
> "bash: update-grub: command not found"
> as if I were the unprivileged user "richard".
>
> All
Il 02/05/22 17:17, Richard Owlett ha scritto:
If logged in as "richard" I can execute su {+ password} and receive a
prompt indicating I'm "root".
"bash: update-grub: command not found"
Bug?
No, it's only an effect of the PATH variable. Try "su -".
.
However if I then enter "update-grub", the response is
"bash: update-grub: command not found"
as if I were the unprivileged user "richard".
All is normal if I had initially been "root" or had become "root" via
System -> Log Out richard .
Bug?
dering whether the data are transferred from the VFS to ext4
> necessarily within the same openat system call or could just be kept
> in the VFS as long as they are not needed elsewhere, i.e. the VFS
> behaving like a cache. In the latter case, since the VFS doesn't
> have a notion of birth
On Mon, May 02, 2022 at 01:10:04AM +0200, Vincent Lefevre wrote:
> On 2022-04-30 14:06:53 +0200, to...@tuxteam.de wrote:
[...]
> > It sure looks like a bug. But it would be a bug at a spot where one would
> > expect that it should have bitten oodles of other people by now, so t
like a cache. In the latter case, since the VFS doesn't
> have a notion of birth timestamp (from the code I've read), a bug
> in the VFS code could explain the behavior I had observed. This is
> the only explanation I could have.
At this point, you should seriously consider asking the Linu
e VFS as long as they are not needed elsewhere, i.e. the VFS
behaving like a cache. In the latter case, since the VFS doesn't
have a notion of birth timestamp (from the code I've read), a bug
in the VFS code could explain the behavior I had observed. This
On 2022-04-30 14:06:53 +0200, to...@tuxteam.de wrote:
> On Sat, Apr 30, 2022 at 10:33:34AM +0200, Thomas Schmitt wrote:
> > I understand that Vincent Lefevre suspects these discrepancies to be a bug
> > in the ext4 driver. I rather suspect that ext4 is ok and that we observe
Hi,
Curt wrote:
> What does the following mean, then, in that light:
> Because of delayed allocation and other performance optimizations, ext4's
> behavior of writing files to disk is different from ext3. In ext4, when a
> program writes to the file system, it is not guaranteed to be
On Sat, Apr 30, 2022 at 12:31:07PM -, Curt wrote:
> On 2022-04-30, Thomas Schmitt wrote:
> >
> > Indeed. With normal filesystem operations there should be no need to call
> > something like sync(2) in order to get a consistent representation of the
> > current filesystem state.
> >
>
> What
On 2022-04-30, Thomas Schmitt wrote:
>
> Indeed. With normal filesystem operations there should be no need to call
> something like sync(2) in order to get a consistent representation of the
> current filesystem state.
>
What does the following mean, then, in that light:
Because of delayed
th via the operating
system facilities is the cache's view. The disk's view will become
consistent with that at some time in the future (at least we hope
that).
[...]
> I understand that Vincent Lefevre suspects these discrepancies to be a bug
> in the ext4 driver. I rather suspect that ext4 i
and
close the file.
The file content indicates that it was written shortly after the script
began.
I understand that Vincent Lefevre suspects these discrepancies to be a bug
in the ext4 driver. I rather suspect that ext4 is ok and that we observe
the effects of some other glitch which caused the ext4
On Fri, Apr 29, 2022 at 09:41:23PM +0200, sp...@caiway.net wrote:
> On Fri, 29 Apr 2022 13:45:15 -0400
>
> > linux caches file system pages in memory
>
> how does one force to refresh this memory with a command?
What do you mean by "refresh"? What's in the cache is always
the "freshest"
On Fri, 29 Apr 2022 13:45:15 -0400
> linux caches file system pages in memory
how does one force to refresh this memory with a command?
Thanks!
On 4/29/2022 10:20 AM, duh wrote:
On 4/27/22 11:05 PM, Greg Wooledge wrote:
Having skimmed over a number of the replies, and really not being
qualified, may I just
toss out a probably useless ideas to use the "sync" command. Looking at
the 'man sync'
shows at the bottom several
On 4/27/22 11:05 PM, Greg Wooledge wrote:
On Wed, Apr 27, 2022 at 10:45:09PM -0400, Stefan Monnier wrote:
Another option might be that your system's time was "reset".
This shouldn't happen, but it can happen if your NTP was down, the
machine got out-of-sync over time and you restart the NTP
ly thought of a possible hardware problem, but
they were common and unrelated. They are triggered by Wine, which is
executed by my script (as I also test MPFR under Wine).
My bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010209
(either the kernel is really doing silly things, or th
en back to the
actual FS.
When I did
tail -n 30 mpfrtests.*.out; ll mpfrtests.*.out
this had the effect to look at the entries in the current directory.
For some reason (a bug occurring under some particular conditions?),
the dirty state due to the data written above to the VFS was ignored,
s
Hi,
Vincent Lefevre wrote:
> and one with
> openat(AT_FDCWD, "….out", O_WRONLY|O_CREAT|O_APPEND, 0666
> <... openat resumed>) = 3
> about 30 seconds later.
Oh. So the script was still running when the file finally appeared to lt,
tail, and ll ?
Is the text snippet " <... openat resumed>"
On 2022-04-27 22:45:09 -0400, Stefan Monnier wrote:
> Another option might be that your system's time was "reset".
> This shouldn't happen, but it can happen if your NTP was down, the
> machine got out-of-sync over time and you restart the NTP server at
> which point it may(!) decide to jump the
On Wed, Apr 27, 2022 at 10:45:09PM -0400, Stefan Monnier wrote:
> Another option might be that your system's time was "reset".
> This shouldn't happen, but it can happen if your NTP was down, the
> machine got out-of-sync over time and you restart the NTP server at
> which point it may(!) decide
my shell history for 6 years.
This was the first time I noticed such an issue. But if this is a
kernel bug, it may be a new bug.
> If so, you could set up a script that sometimes reproduces, and run it
> in a loop until you get the erroneous behavior.
I'll try to do that.
> Of course
On Wed, Apr 27, 2022 at 03:11:22PM +0200, Vincent Lefevre wrote:
> So, perhaps there were no issues with openat, but when reading
> the directory, the file could not be found because some internal
> structures might have been incomplete.
If so, this is a bug at the kernel level
e RAM.
I was thinking of a potentially specific FS cache. But perhaps this
is not related to the CPU at all. It could be that a potential bug
(either in the kernel code or in the compiler) would affect some
system calls but not others. So, the ">> $out" done in the script
would work, bu
Hi,
Vincent Lefevre wrote:
> the issue [...] is probably unlikely to occur again.
In this case we will hardly be able to find an explanation.
> However, there's also the fact that the birth time was 30 seconds
> ahead of the actual file creation, while there was no lockup.
Yes, your
ould not show up in stat(1)
> or ls(1) but the script can happily do
> ... >> "$out"
> Each of these lines is supposed to do a name lookup of the file.
unless there is some caching bug. The script is likely to run on
the same CPU core, so that the file would still
Hi,
i wrote:
> > So if it got created by the script, maybe it was deleted or renamed
> > shortly afterwards and created again 30 seconds later ?
Vincent Lefevre wrote:
> The script doesn't do that. The file is created with
> echo "* $fqdn ($(${1:-.}/config.guess) / ${line#PROC:})" > "$out"
>
On 2022-04-26 14:18:58 -0400, Stefan Monnier wrote:
> > On an ext4 filesystem, I got a file born 30 seconds after its
> > actual creation. Is this a bug?
>
> I doubt it.
> Note that a file's atime/mtime/ctime is a property of the file itself,
> whereas "appearing
On 2022-04-26 12:47:53 -0500, Nicholas Geovanis wrote:
> On Tue, Apr 26, 2022 at 12:37 PM Nicholas Geovanis
> wrote:
>
> > On Tue, Apr 26, 2022 at 8:45 AM Vincent Lefevre
> > wrote:
> >
> >> On an ext4 filesystem, I got a file born 30 seconds after its
On 2022-04-26 19:01:26 +0200, Thomas Schmitt wrote:
> It looks as if the file indeed does not exist when you inquire it.
> So if it got created by the script, maybe it was deleted or renamed
> shortly afterwards and created again 30 seconds later ?
The script doesn't do that. The file is created
On Tue, Apr 26, 2022 at 01:31:02PM +, Schwibinger Michael wrote:
>
> Good afternoon.
> Thank You
>
> We dont use WIFI.
>
> Desktops
>
> We do
> connect with cable to the WWW.
> Also mouse and keyboard is with cable.
>
OK: in many ways that makes it easier. I would still suggest the
On Tue, Apr 26, 2022 at 12:37 PM Nicholas Geovanis
wrote:
> On Tue, Apr 26, 2022 at 8:45 AM Vincent Lefevre
> wrote:
>
>> On an ext4 filesystem, I got a file born 30 seconds after its
>> actual creation. Is this a bug?
>>
>
> Only experimentation can really
On Tue, Apr 26, 2022 at 8:45 AM Vincent Lefevre wrote:
> On an ext4 filesystem, I got a file born 30 seconds after its
> actual creation. Is this a bug?
>
Only experimentation can really back me up on this, but consider the
following:
Every time you use the "|" operator o
Hi,
Vincent Lefevre wrote:
> This script creates a file mpfrtests.cventin.lip.ens-lyon.fr.out
> very early. But the first attempts to look at this file failed:
It looks as if the file indeed does not exist when you inquire it.
So if it got created by the script, maybe it was deleted or renamed
On Tue, 26 Apr 2022 09:32:23 -0400
Greg Wooledge wrote:
...
> Firmware is executable code that runs inside of a device (such as a
> network interface) rather than in your CPU.
>
> Many modern devices require some non-free firmware in order to perform
> their duties correctly. This is
On Tue, Apr 26, 2022 at 01:41:07PM +, Schwibinger Michael wrote:
> What does mean
>
> firmware is free
> firmware is not free?
Firmware can be free OR non-free.
Firmware for wireless interfaces is ALMOST ALWAYS non-free, because of
proprietary secrets that the wireless chip manufacturer is
: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry
On Mon, Apr 25, 2022 at 07:18:48PM +0100, Brian wrote:
> On Mon 25 Apr 2022 at 17:24:29 +, Andrew M.A. Cater wrote:
>
> > On Mon, Apr 25, 2022 at 06:15:40PM
---Amateur in Linux...Problem: Debian LXDE
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry
Am Montag, 25. April 2022, 12:58:48 CEST schrieb Schwibinger Michael:
Best version, if you do not want to have administration work, would be
Debian-11 (which is bullseye). You should choose "s
On an ext4 filesystem, I got a file born 30 seconds after its
actual creation. Is this a bug?
I know that such issues can be observed with NFS, but here this
is just a local ext4 filesystem.
Here are the details.
I started a shell script:
cventin:~> ps -p 667828 -o lstart,
: Debian LXDE
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry
On Tue, Apr 26, 2022 at 01:27:39PM +, Schwibinger Michael wrote:
> What is firmware?
> Do I need it?
> Is it dangerous?
Firmware is executable code that runs inside of a device (such as a
network interface) ra
: Here Newbie---Amateur in Linux...Problem: Debian LXDE
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry
Hello Sophie,
>
>
> >
> >
> >
> > Good afternoon.
> >
> > Thank You.
> >
> > We do backup eve
On Tue, Apr 26, 2022 at 01:27:39PM +, Schwibinger Michael wrote:
> What is firmware?
> Do I need it?
> Is it dangerous?
Firmware is executable code that runs inside of a device (such as a
network interface) rather than in your CPU.
Many modern devices require some non-free firmware in order
LXDE
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry
On Mon, Apr 25, 2022 at 06:15:40PM +0100, Brian wrote:
> On Mon 25 Apr 2022 at 16:59:57 +, Andrew M.A. Cater wrote:
>
> > Hello Sophie,
> > >
> > >
> > > > _
On Mon, Apr 25, 2022 at 07:18:48PM +0100, Brian wrote:
> On Mon 25 Apr 2022 at 17:24:29 +, Andrew M.A. Cater wrote:
>
> > On Mon, Apr 25, 2022 at 06:15:40PM +0100, Brian wrote:
> > > On Mon 25 Apr 2022 at 16:59:57 +, Andrew M.A. Cater wrote:
> > >
> > > > Hello Sophie,
> > > > >
> > >
On Mon 25 Apr 2022 at 17:24:29 +, Andrew M.A. Cater wrote:
> On Mon, Apr 25, 2022 at 06:15:40PM +0100, Brian wrote:
> > On Mon 25 Apr 2022 at 16:59:57 +, Andrew M.A. Cater wrote:
> >
> > > Hello Sophie,
> > > >
> > > >
> > > > >
> > > > >
> > > > >
>
On Mon, Apr 25, 2022 at 06:15:40PM +0100, Brian wrote:
> On Mon 25 Apr 2022 at 16:59:57 +, Andrew M.A. Cater wrote:
>
> > Hello Sophie,
> > >
> > >
> > > >
> > > >
> > > >
> > > > Good afternoon.
> > > >
> > > > Thank You.
> > > >
> > > > We do backup
On Mon 25 Apr 2022 at 16:59:57 +, Andrew M.A. Cater wrote:
> Hello Sophie,
> >
> >
> > >
> > >
> > >
> > > Good afternoon.
> > >
> > > Thank You.
> > >
> > > We do backup every evening.
> > >
> > > What version of Debian from Debian URL is the best do
Hello Sophie,
>
>
> >
> >
> >
> > Good afternoon.
> >
> > Thank You.
> >
> > We do backup every evening.
> >
> > What version of Debian from Debian URL is the best do download and burn on
> > CD?
> >
We still don't know what the actual computer you use is
Am Montag, 25. April 2022, 12:58:48 CEST schrieb Schwibinger Michael:
Best version, if you do not want to have administration work, would be
Debian-11 (which is bullseye). You should choose "stable", which is well
tested and does not have much changes in the future.
Of course you will chose the
09:55
An: Schwibinger Michael
Betreff: Re: AW: AW: Here Newbie---Amateur in Linux...Problem: Debian LXDE
cannot boot.. Is it destroyed?//Second try Hotmail bug Sorry
Am Montag, 25. April 2022, 11:35:38 CEST schrieben Sie:
If you have no important data, a fresh installation will do the best.
Do
Good morning
Thank You
Is the best solution
to destroy the system
download LIVE CD Debian 11 64
LXDE
and install with ext3?
Regards
Sophie
Can ext3 files burned on CD and transported to Ubuntu and WIN PCs?
Good morning
Thank You
Is the best solution
to destroy the system
On Tue 22 Mar 2022 at 08:49:12 (+0100), Harald Dunkel wrote:
> apparently it takes about 10 minutes between filing a bug report (no
> attachments) and sending the confirmation EMail. Thats quite a long
> time. Imagine you have to forward Debian's bug number to your own
>
On Tue 22 Mar 2022 at 07:25:55 -0400, Greg Wooledge wrote:
> On Tue, Mar 22, 2022 at 08:49:12AM +0100, Harald Dunkel wrote:
> > apparently it takes about 10 minutes between filing a bug report (no
> > attachments) and sending the confirmation EMail. Thats quite a long
> > t
David Wright wrote:
> On Mon 21 Mar 2022 at 15:07:45 (+), Dr. Alex Sheppard wrote:
> > On 21/03/2022 14:02, Dan Ritter wrote:
> > > Dr. Alex Sheppard wrote:
> > So, unless anyone can explain otherwise, I think there is a bug to
> > report against unattended-u
On Tue, Mar 22, 2022 at 08:49:12AM +0100, Harald Dunkel wrote:
> apparently it takes about 10 minutes between filing a bug report (no
> attachments) and sending the confirmation EMail. Thats quite a long
> time. Imagine you have to forward Debian's bug number to your own
> in-house
Hi folks,
apparently it takes about 10 minutes between filing a bug report (no
attachments) and sending the confirmation EMail. Thats quite a long
time. Imagine you have to forward Debian's bug number to your own
in-house BTS.
There are about 10^6 bug reports in Debian's BTS. Maybe 1
one of them and thereby breaking DNS on a
> > > client's network.
> > >
> > > Is this a bug in unattended upgrades, or a bug in apt or dpkg? Here
> > > is
> > > an extract from my unattended-upgrades.log to illustrate.
It might help to check
On 21/03/2022 14:02, Dan Ritter wrote:
Dr. Alex Sheppard wrote:
Hi,
Unattended upgrades ended up removing some of the packages it was was
going to upgrade ... bind9 being one of them and thereby breaking DNS on a
client's network.
Is this a bug in unattended upgrades, or a bug
Dr. Alex Sheppard wrote:
> Hi,
>
> Unattended upgrades ended up removing some of the packages it was was
> going to upgrade ... bind9 being one of them and thereby breaking DNS on a
> client's network.
>
> Is this a bug in unattended upgrades, or a bug
Hi,
Unattended upgrades ended up removing some of the packages it was
was going to upgrade ... bind9 being one of them and thereby breaking
DNS on a client's network.
Is this a bug in unattended upgrades, or a bug in apt or dpkg? Here
is an extract from my unattended-upgrades.log
This bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895378
sky2: sky2: did not recover correctly after waking up from S3
seems to be fixed on Ubuntu here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921
Will this fix get to Debian? I guess it will go up to kernel
On Sun, 13 Mar 2022, Cindy Sue Causey wrote:
On 3/12/22, Brad Rogers wrote:
On Sun, 13 Mar 2022 09:19:52 +1100
Charlie wrote:
Discovered that when I looked for the mailing list on the net.
I dare not say googled because there is some controversy about
IKWYM, but in most
On Sun 13 Mar 2022 at 16:02:25 (+), Brad Rogers wrote:
> On Sun, 13 Mar 2022 11:51:03 -0400
> Cindy Sue Causey wrote:
> > I remember very early on where there was at least one headline that
> > said Google was considering court action over the use of its name as a
> > verb (copyright,
On Sun, Mar 13, 2022, 11:26 AM mick crane wrote:
> On 2022-03-13 16:02, Brad Rogers wrote:
> > On Sun, 13 Mar 2022 11:51:03 -0400
> > Cindy Sue Causey wrote:
> >
> > Hello Cindy,
> >
> >> said Google was considering court action over the use of its name as a
> >
> > Against who? I mean, since
On 2022-03-13 16:02, Brad Rogers wrote:
On Sun, 13 Mar 2022 11:51:03 -0400
Cindy Sue Causey wrote:
Hello Cindy,
said Google was considering court action over the use of its name as a
Against who? I mean, since the term was used by everyone (for certain
values of everyone), short of suing
On Sun, 13 Mar 2022 11:51:03 -0400
Cindy Sue Causey wrote:
Hello Cindy,
>said Google was considering court action over the use of its name as a
Against who? I mean, since the term was used by everyone (for certain
values of everyone), short of suing the *entire* population, what did
they
401 - 500 of 8562 matches
Mail list logo
