Hi,
If like me, you've been eagerly awaiting debian11 to
get bind-9.16.15, which finally lets you implement
DNSSEC extremely easily on debian stable, I have a
warning.
Bind has a dnssec-policy {} stanza for defining your
own policy if you're feeling adventurous, but there's
also a default
On Sun, 15 Aug 2021 10:32:01 -0400 Greg Informed me about Re:
Upgrade from buster
> On Sun, Aug 15, 2021 at 02:34:59PM +1000, Charlie wrote:
> > But didn't upgrade because of failure running
> > /usr/sbin/apt-listbugs apt
>
> I'm wondering if the failures of
Hi,
On 2021-08-15 10:26 p.m., Jeremy Ardley wrote:
>
> On 16/8/21 10:17 am, Weaver wrote:
>>
>> Any idiot can edit a page there.
>> Cheers!
>>
>> Harry.
>>
> And they frequently do!
>
> Yesterday I looked up 'harmonic analysis' of which I am a subject
> expert. The article was virtually
On 2021-08-15 10:26 p.m., Jeremy Ardley wrote:
>
> On 16/8/21 10:17 am, Weaver wrote:
>>
>> Any idiot can edit a page there.
>> Cheers!
>>
>> Harry.
>>
> And they frequently do!
>
> Yesterday I looked up 'harmonic analysis' of which I am a subject
> expert. The article was virtually
On 16/8/21 10:17 am, Weaver wrote:
Any idiot can edit a page there.
Cheers!
Harry.
And they frequently do!
Yesterday I looked up 'harmonic analysis' of which I am a subject
expert. The article was virtually incomprehensible to me. But worse, it
almost completely missed what it is about -
On 16-08-2021 11:56, Jeremy Ardley wrote:
> On 16/8/21 9:45 am, Weaver wrote:
>>
>> By reputation, the list is unmoderated, and that's the way it used to
>> be.
>> It still bears the token title of an unmoderated list but, in reality, a
>> small collective of the politically correct have placed it
On 16/8/21 9:45 am, Weaver wrote:
By reputation, the list is unmoderated, and that's the way it used to
be.
It still bears the token title of an unmoderated list but, in reality, a
small collective of the politically correct have placed it under their
auspices to moderate it. They have all the
On 16-08-2021 11:29, lou wrote:
> Andrew, i thought you r moderator because you post monthly list guideline
>
> and you speak kindly with some authority when some list user deviate
By reputation, the list is unmoderated, and that's the way it used to
be.
It still bears the token title of an
El 15/8/21 a las 17:16, miguel angel gonzalez escribió:
Hola,
Ya está Debian 11 estable disponible, desde ayer. Uno de los pasos es
cambiar los repositorios, pero no sólo los de seguridad, todos.
Te dejo la información oficial:
El 15/8/21 a las 16:07, JavierDebian escribió:
El 15/8/21 a las 11:28, José Manuel (Abogado) escribió:
Hola
Unas preguntas:
1º ¿ya es versión estable Debian 11 (bullseye)? si es sí, debemos
cambiar el repositorio de seguridad por este:
deb http://security.debian.org/debian-security
On 2021-08-15 9:29 p.m., lou wrote:
> Andrew, i thought you r moderator because you post monthly list guideline
>
> and you speak kindly with some authority when some list user deviate
>
Andrew is a active community member who gives lots of time for all of
us. I think he's (pick a word) in
Andrew, i thought you r moderator because you post monthly list guideline
and you speak kindly with some authority when some list user deviate
Synaptic has a button to (essentially) run "apt update" It's in the upper left
corner of the window and labeled "Reload" and if you hover over it, it says
"reload the package information to become informed about new, removed or
upgraded software packages".
HTH!
Rick
On 16/08/2021 7:19 am, raf wrote:
It's working now on the original VM. Someone else reported
that keys have finally made it to a German mirror, solving
a similar problem for them. I guess I was having the same
A problem with the Australian mirror. But maybe that's just
a guess. The keys
On Sun, Aug 15, 2021 at 06:47:34PM +1000, raf wrote:
> On Sun, Aug 15, 2021 at 08:24:13AM +0200, john doe
> wrote:
>
> > The below assumes that 'sources.list' is set only for bullseye
> >
> > Some hints more than an answer:
> > - Try to remove the gpg keys in '/etc/apt' directory.
> > - Try
Hello everybody. The DVD-1 image is coming with contrib enabled on the cd-rom,
security and update lines. This is normal? The netinstall image is just with
main.
P.S.: Sorry for my english.
Ramon Mulin
Professor de História
On 2021-08-15 2:25 p.m., Brian wrote:
> On Sun 15 Aug 2021 at 20:13:55 +0200, Roger Price wrote:
>
>> man synaptic says « It allows you to perform all actions of the command line
>> tool apt-get in a graphical environemnt. »
>>
>> In the help manual I read « Reload the package information to be
On 2021-08-15 3:34 p.m., Brian wrote:
> On Sun 15 Aug 2021 at 22:13:07 +0300, Gunnar Gervin wrote:
>
>> Hi.
>> After I put EFI in sda1 Refracta installer was not satisfied and told me to
>> put 'boot installer' in, and write some (unspecified) text in fstab, but
>> wasn't in ETC.
>
> [...]
>
Hi,
On 2021-08-15 3:13 p.m., Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me
> to put 'boot installer' in, and write some (unspecified) text in fstab,
> but wasn't in ETC.
>
> How and what to write in fstab?
>
> You tell me to specify
On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote:
> On Sun, Aug 15, 2021 at 10:13:07PM +0300, Gunnar Gervin wrote:
>> Hi.
>> After I put EFI in sda1 Refracta installer was not satisfied and told me to
>> put 'boot installer' in, and write some (unspecified) text in fstab, but
>> wasn't in ETC.
On Sat, Aug 14, 2021 at 10:01:37PM +0200, Marco Möller wrote:
> Dear moderators, I would appreciate if you could interfere.
> This list recently is flooded with never ending arguing, and respect and
> politeness too often got lost.
>
> Same here as already for Michael Howards "Fwd: [OFFTOPIC]
Hi,
On 2021-08-15 3:13 p.m., Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me
> to put 'boot installer' in, and write some (unspecified) text in fstab,
> but wasn't in ETC.
>
> How and what to write in fstab?
>
Hi,
On 2021-08-15 3:13 p.m., Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me
> to put 'boot installer' in, and write some (unspecified) text in fstab,
> but wasn't in ETC.
>
> How and what to write in fstab?
>
> You tell me to specify
Hi,
On Sun, Aug 15, 2021 at 10:15:45PM +0300, илья пащук wrote:
> docker image of debian bullseye should be updated to reflect it's release.
There is a message on debian-boot (and -devel) here about it:
https://lists.debian.org/debian-boot/2021/08/msg00096.html
I'm not sure that the Debian
On Sun, Aug 15, 2021 at 10:13:07PM +0300, Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me to
> put 'boot installer' in, and write some (unspecified) text in fstab, but
> wasn't in ETC.
>
> How and what to write in fstab?
>
> You tell me to
Bonjour,
Ca y estn elle est arrivée la Debian 11.
https://bits.debian.org/2021/08/bullseye-released.html
Mais peut-être que vous le saviez déjà !?
Christophe
--
Debian Duster 10.8|Kernel 4.19.0-14-amd64|Xorg 1.20.4 & Xfce 4.12
http://www.debian.org #
Hola,
Us escric ja des d'una Debian 11 escriptori xfce4 actualitzada des de
Debian 10.10.
Ha conservat totes les dades del directori d'inici (/home/usuari); n'havia
fet còpia prèviament per si de cas.
* Avisos que he tingut durant l'actualització (fitxers que podien quedar
substituïts):
On Sun, 15 Aug 2021 21:32:43 +0200 (CEST)
Roger Price wrote:
Hello Roger,
>Thanks to all those who replied. It should have seen and understood
>"reload"
To be fair, it's not immediately obvious what Reload does. It could just
be the displayed list of packages, for example. Especially if
On Sun 15 Aug 2021 at 22:15:45 +0300, илья пащук wrote:
> docker image of debian bullseye should be updated to reflect it's release.
Sounds like a good idea. Please submit a wishlist bug against the
package.
--
Brian.
On Sun 15 Aug 2021 at 22:13:07 +0300, Gunnar Gervin wrote:
> Hi.
> After I put EFI in sda1 Refracta installer was not satisfied and told me to
> put 'boot installer' in, and write some (unspecified) text in fstab, but
> wasn't in ETC.
[...]
This isn't a concern of Debian. Please take it
hello.
docker image of debian bullseye should be updated to reflect it's release.
On Sun, 15 Aug 2021, Brad Rogers wrote:
On Sun, 15 Aug 2021 20:13:55 +0200 (CEST)
Roger Price wrote:
always run apt update manually before clicking on synaptic?
No, just hit Synaptic's reload button.
Thanks to all those who replied. It should have seen and understood "reload".
Roger
Hi.
After I put EFI in sda1 Refracta installer was not satisfied and told me to
put 'boot installer' in, and write some (unspecified) text in fstab, but
wasn't in ETC.
How and what to write in fstab?
You tell me to specify question.
How to specify a total mess?
I'm trying to put a (Debian fork),
On Sun, 15 Aug 2021 20:45:17 +0200 (CEST), Roger Price wrote:
> On Sun, 15 Aug 2021, Brian wrote:
> > On Sun 15 Aug 2021 at 20:13:55 +0200, Roger Price wrote:
> >
> > > Does this mean that synaptic does _not_ call apt update, and that I
> > > should always run apt update manually before clicking
Greg Wooledge [2021-08-15 10:30:27] wrote:
> On Sun, Aug 15, 2021 at 04:13:37PM +0200, sp...@caiway.net wrote:
>> lou what about
>> # apt install xorg fluxbox
>>
>> $ startx
>
> In theory that might work (you may also need firmware), but the amount
> of bandwidth you'd burn through downloading
On Sun, 15 Aug 2021 20:13:55 +0200 (CEST)
Roger Price wrote:
Hello Roger,
>always run apt update manually before clicking on synaptic?
No, just hit Synaptic's reload button.
--
Regards _
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only
> You don't really get that far if your root FS is unmountable.
Hmm... if it truly can't be mounted, then the system can't read
`/etc/passwd` and then whether there is a root account or not makes
no difference.
In the "usual" case where the root FS is readable but fsck found errors,
then indeed
On Sun, 15 Aug 2021, Brian wrote:
On Sun 15 Aug 2021 at 20:13:55 +0200, Roger Price wrote:
Does this mean that synaptic does _not_ call apt update, and that I should
always run apt update manually before clicking on synaptic?
Some experiments suggest that this is the case.
You would have to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
‐‐‐ Original Message ‐‐‐
On Sunday, August 15, 2021 12:13 PM, Roger Price wrote:
> Does this mean that synaptic does not call apt update, and that I should
> always run apt update manually before clicking on synaptic?
Not sure, but I
On Sun, 15 Aug 2021 20:13:55 +0200 (CEST)
Roger Price wrote:
> man synaptic says « It allows you to perform all actions of the
> command line tool apt-get in a graphical environemnt. »
>
> In the help manual I read « Reload the package information to be
> aware of the latest versions available:
On Sat, 2021-08-14 at 20:44 +0100, Michael Howard wrote:
> and her is an off list reply reply from the less than honourable Polyna
I killfiled them weeks ago, I don't know why people do just do similar
and move on...
On Sun 15 Aug 2021 at 20:13:55 +0200, Roger Price wrote:
> man synaptic says « It allows you to perform all actions of the command line
> tool apt-get in a graphical environemnt. »
>
> In the help manual I read « Reload the package information to be aware of
> the latest versions available: »
>
man synaptic says « It allows you to perform all actions of the command line
tool apt-get in a graphical environemnt. »
In the help manual I read « Reload the package information to be aware of the
latest versions available: »
Does this mean that synaptic does _not_ call apt update, and that
On Sun, Aug 15, 2021, 10:58 Georgios wrote:
> Hi!
> I upgraded from debian 10 to debian 11 today and I noticed that a gnome
> extension I really liked dont work on the latest gnome.
>
George,
See:
https://github.com/passingthru67/workspaces-to-dock
- Keith
Hi!
I upgraded from debian 10 to debian 11 today and I noticed that a gnome
extension I really liked dont work on the latest gnome.
More specifically I used "workspace to dock" in order to have access to
workspaces.
I just put the mouse on the right side and the workspace list that is
viewed on
Hi Evelyn,
On Sun, Aug 15, 2021 at 06:00:08PM +0200, Evelyn Pereira Souza wrote:
> E: The repository 'http://security.debian.org/debian-security
> bullseye/updates Release' does not have a Release file.
A few people have by now pointed out the specific cause of your
problem, but the root cause
Am Sonntag, 15. August 2021, 18:15:36 CEST schrieb Frank:
Yes, this was a typo, sorry for that.
Best
Hans
> Op 15-08-2021 om 18:01 schreef Hans:
> > Hi all,
> >
> > discovered something. It looks like the keys are still not synced to the
> > mirrors.
> >
> > I changed from ftp.de.debian.org
Hola,
Ya está Debian 11 estable disponible, desde ayer. Uno de los pasos es
cambiar los repositorios, pero no sólo los de seguridad, todos.
Te dejo la información oficial:
https://www.debian.org/releases/bullseye/arm64/release-notes/ch-upgrading.es.html
Un saludo.
El dom, 15 ago 2021 a las
Op 15-08-2021 om 18:01 schreef Hans:
Hi all,
discovered something. It looks like the keys are still not synced to the
mirrors.
I changed from ftp.de.debian.org to deb.debian.org, and all is working like a
charm.
So, I suppose, this issue might be solved.
But it would be nice to add a package
> deb http://security.debian.org/debian-security bullseye/updates main contrib
> non-free
> deb-src http://security.debian.org/debian-security bullseye/updates main
> contrib non-free
I think you are missing bullseye-security. I have this:
deb http://mirrors.linode.com/debian-security/
On Sun, Aug 15, 2021 at 12:06:18PM -0400, The Wanderer wrote:
> On 2021-08-15 at 12:00, Evelyn Pereira Souza wrote:
>
> > Hi
> >
> > apt-get update
> > Ign:1 http://security.debian.org/debian-security bullseye/updates InRelease
> > Err:2 http://security.debian.org/debian-security
Am Sonntag, 15. August 2021, 18:00:08 CEST schrieb Evelyn Pereira Souza:
Hi Evelyn,
the entry in sources.list has changed, it is now:
deb http://deb.debian.org/debian-security bullseye-security main contrib
non-free
deb-src http://deb.debian.org/debian-security bullseye-security main contrib
On Sun 15 Aug 2021 at 12:06:18 -0400, The Wanderer wrote:
> On 2021-08-15 at 12:00, Evelyn Pereira Souza wrote:
>
> > Hi
> >
> > apt-get update
> > Ign:1 http://security.debian.org/debian-security bullseye/updates InRelease
> > Err:2 http://security.debian.org/debian-security bullseye/updates
On 2021-08-15 at 12:00, Evelyn Pereira Souza wrote:
> Hi
>
> apt-get update
> Ign:1 http://security.debian.org/debian-security bullseye/updates InRelease
> Err:2 http://security.debian.org/debian-security bullseye/updates Release
>404 Not Found [IP: 199.232.138.132 80]
> deb
Hi all,
discovered something. It looks like the keys are still not synced to the
mirrors.
I changed from ftp.de.debian.org to deb.debian.org, and all is working like a
charm.
So, I suppose, this issue might be solved.
But it would be nice to add a package with the actual keys into the
Hi
apt-get update
Ign:1 http://security.debian.org/debian-security bullseye/updates InRelease
Err:2 http://security.debian.org/debian-security bullseye/updates Release
404 Not Found [IP: 199.232.138.132 80]
Hit:3 http://mirror.init7.net/debian bullseye InRelease
Hit:4
On 15.08.21 15:46, Andrew M.A. Cater wrote:
I would suggest installing Debian 11 - just released - for two reasons:
Yes working with Bullseye.
happy weekend
Evelyn
OpenPGP_0x61776FA8E38403FB.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
On Sun 15 Aug 2021 at 10:48:58 (-0400), Greg Wooledge wrote:
> On Sun, Aug 15, 2021 at 08:19:35PM +0700, Ken Heard wrote:
> > Having noted that the release of Bullseye is imminent I decided to
> > use the RC2 iteration of Bullseye rather than Buster.
> > I consequently downloaded file
On Sun, Aug 15, 2021 at 11:00:26AM -0400, Stefan Monnier wrote:
> > You don't really get that far if your root FS is unmountable.
>
> Hmm... if it truly can't be mounted, then the system can't read
> `/etc/passwd` and then whether there is a root account or not makes
> no difference.
That's
Yes, but did not work.
Strangely, the entry for bullseye-security seem to work (as there is an
existing key).
Best
Hans
> Have you tried adding *[trusted=yes]* inside the sources.list file that
> contain reference to this repository.
signature.asc
Description: This is a digitally signed
Op 15-08-2021 om 16:51 schreef Hans:
Am Sonntag, 15. August 2021, 16:36:05 CEST schrieb Brian:
Yes, you are very right!
There isn't any such thing as being "too critical" when it comes to
technical matters :).
A link to the page you were looking at might help.
To everyone:
I have still the
On Sun 15 Aug 2021 at 00:41:30 (+0300), ellanios82 wrote:
> On 8/15/21 12:31 AM, Greg Wooledge wrote:
> > Press Ctrl-Alt-F2 to attempt to reach a text console. If that's
> > successful, then he can login there (as root) and attempt to install
> > whatever's required to fix the problem
>
> -
On Sun, Aug 15, 2021 at 11:00:26AM -0400, Stefan Monnier wrote:
> Of course, the existence of a root password can occasionally be handy
> for things like `rsync` (strictly speaking, you can probably arrange
> for rsync to first log in as a normal user and then use `sudo`, but
> it requires a fair
On 2021-08-15 10:51 a.m., Hans wrote:
> Am Sonntag, 15. August 2021, 16:36:05 CEST schrieb Brian:
> Yes, you are very right!
>>
>> There isn't any such thing as being "too critical" when it comes to
>> technical matters :).
>>
>> A link to the page you were looking at might help.
>
> To
On Sun 15 Aug 2021 at 15:36:05 (+0100), Brian wrote:
> On Sun 15 Aug 2021 at 16:13:51 +0200, Hans wrote:
>
> > Yeah, not quite. I was already aware, that https won't improve security
> > much.
> >
> > I just wondered, why the docu once is telling "use https" and once "http".
> > If
> > only
Am Sonntag, 15. August 2021, 16:36:05 CEST schrieb Brian:
Yes, you are very right!
>
> There isn't any such thing as being "too critical" when it comes to
> technical matters :).
>
> A link to the page you were looking at might help.
To everyone:
I have still the problem, that the
On Sun, Aug 15, 2021 at 08:19:35PM +0700, Ken Heard wrote:
> Having noted that the release of Bullseye is imminent I decided to
> use the RC2 iteration of Bullseye rather than Buster.
> I consequently downloaded file 'Debian-bullseye-DI-rc2-amd4-netinst.iso'
I don't know where you're getting your
On Sun, 15 Aug 2021 10:30:27 -0400
Greg Wooledge wrote:
> On Sun, Aug 15, 2021 at 04:13:37PM +0200, sp...@caiway.net wrote:
> > lou what about
> > # apt install xorg fluxbox
> >
> > $ startx
>
> In theory that might work (you may also need firmware), but the amount
> of bandwidth you'd burn
The Wanderer wrote:
...
> I had enough trouble with this at the last Debian release, and came
> close enough to having trouble with it again this time, that I want to
> make sure the solution is available and findable for anyone else who may
> need it.
...
considering i use only testing in my
On Sun, Aug 15, 2021 at 08:49:49AM +0200, to...@tuxteam.de wrote:
> [trying to enter single user mode requires a root password]
>
> Of course, there are ways around that, but all of them involve having
> access to another living instance of an operating system,
Not all. You can supply kernel
On Sun 15 Aug 2021 at 16:13:51 +0200, Hans wrote:
> Yeah, not quite. I was already aware, that https won't improve security much.
>
> I just wondered, why the docu once is telling "use https" and once "http". If
> only using https or either http, this would not create confuseness.
>
> Looks
On Sun, Aug 15, 2021 at 02:34:59PM +1000, Charlie wrote:
> But didn't upgrade because of failure running
> /usr/sbin/apt-listbugs apt
I'm wondering if the failures of apt-listbugs are related to the
failure of the bugs.debian.org web site. It's gotta be related, right?
In your particular case,
On Sun, Aug 15, 2021 at 04:13:37PM +0200, sp...@caiway.net wrote:
> lou what about
> # apt install xorg fluxbox
>
> $ startx
In theory that might work (you may also need firmware), but the amount
of bandwidth you'd burn through downloading *all* those packages each
and every time you boot the
Hola
Unas preguntas:
1º ¿ya es versión estable Debian 11 (bullseye)? si es sí, debemos
cambiar el repositorio de seguridad por este:
deb http://security.debian.org/debian-security bullseye-security main
contrib non-free
Gracias de antemano.
--
Un saludo,
José Manuel
Gran Canaria/España
Si
On Sun, 15 Aug 2021 11:30:07 +0800
Jeremy Ardley wrote:
then these X apps are to be run remotely
> On 15/8/21 11:22 am, lou wrote:
> >
> > and what is password for root?
> >
> You should be able to do
>
> sudo passwd root
>
> and set your own password
>
>
Thanks for the tips lou & Jeremy
Yeah, not quite. I was already aware, that https won't improve security much.
I just wondered, why the docu once is telling "use https" and once "http". If
only using https or either http, this would not create confuseness.
Looks like I am too critical. am I not? :)
Best regards
Hans
>
On Sat, Aug 14, 2021 at 11:22:12PM -0400, lou wrote:
>
> On 8/14/21 11:08 PM, Weaver wrote:
> >
> > At the prompt, type `startx'.
> > Depending on permissions, you may need to become root.
> > Cheers!
> >
> > Harry.
> >
>
> startx don't seem to be included in ISO image
>
> and what is
On Sun 15 Aug 2021 at 20:19:35 +0700, Ken Heard wrote:
[Extensive information snipped]
>From Knoppix live check that the Debian installation is on /dev/sda.
Then 'grub-install /dev/sda' and boot.
--
Brian.
On Sun, Aug 15, 2021 at 01:21:24PM +0200, Evelyn Pereira Souza wrote:
> On 15.08.21 10:52, to...@tuxteam.de wrote:
> > You also have a "2019 5k iMac"? Because that is very important in this
> > context.
>
> Here more details about my HW:
>
> # inxi -Fxz
> System:Host: norp Kernel:
On Sun, Aug 15, 2021 at 04:40:31PM +0300, ellanios82 wrote:
>
> - bewildered , am getting stuff like this :
>
>
> GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY F942E0D4E1C726CD
>
- bewildered , am getting stuff like this :
GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY F942E0D4E1C726CD
.
what to try please ??
thanks
.
I recently upgraded a desktop computer by replacing major parts in it
including the mainboard and CPU. I now want to install in it a more up to
date operating system than Wheezy which was the one used before the
upgrade. Having noted that the release of Bullseye is imminent I decided to
use the
On Sun 15 Aug 2021 at 11:36:54 +0200, Hans wrote:
[...]
> Another thing besides this: I am wondering, why the debian documentation
> differs
> between http and https at the entries for the security and the normal
> packages. I would have been expected, that all entries are using https, and
>
On Sun 15 Aug 2021 at 14:13:06 +0200, Sven Hartge wrote:
> Evelyn Pereira Souza wrote:
>
> > My guess is because I use a VPN.
> > Why Debian blocks VPNs?
>
> Because of repeated vandalism to the Wiki. At one point a decision had
> to be made to either restrict the access to certain IP ranges
Evelyn Pereira Souza wrote:
> My guess is because I use a VPN.
> Why Debian blocks VPNs?
Because of repeated vandalism to the Wiki. At one point a decision had
to be made to either restrict the access to certain IP ranges or make
the whole Wiki read-only for everyone.
Grüße,
Sven (not a DD,
Hi
Lots of sites from Debian project I get a 403.
example:
curl -I https://wiki.debian.org/InstallingDebianOn/Apple/iMac/10-1
HTTP/2 403
date: Sun, 15 Aug 2021 11:54:52 GMT
server: Apache
x-content-type-options: nosniff
x-frame-options: sameorigin
referrer-policy: no-referrer
On Sun, Aug 15, 2021 at 12:15:07PM +0300, Reco wrote:
> Hi.
>
> On Sun, Aug 15, 2021 at 08:49:49AM +0200, to...@tuxteam.de wrote:
[...]
> > Up to now, there is exactly one case I am aware of when you'd wish
> > you had a root password: at boot, the root file system is deemed
> > too
On 15.08.21 10:52, to...@tuxteam.de wrote:
You also have a "2019 5k iMac"? Because that is very important in this
context.
Here more details about my HW:
# inxi -Fxz
System:Host: norp Kernel: 4.19.0-17-amd64 x86_64 bits: 64 compiler:
gcc v: 8.3.0
Console: tty 0 Distro: Debian
Hi Eike,
it is not that easy and sadly this does not work. I copied the Release.gpg to
/etc/apt/
trusted.gpg.d/ and renamed it to "debian-archive-bullseye-stable.gpg".
I also get lots of errors, since bullseye chaged something. Please see:
snip
On 8/15/21 4:08 AM, Greg Wooledge wrote:
Why not simply "apt update"?
: i have myself muddled : am getting "NO_PUBKEY"
- what to try, please ?
thank you
regards
.
Thanks, thatdidit.
On Sun, 15 Aug 2021 04:46:16 -0400,
Frank wrote:
>
> Op 15-08-2021 om 08:23 schreef John Covici:
> > Hi. I did a apt-get update changing from buster to bullseye and got
> > the above message -- should I just wait a few days and try again or
> > something else?
> >
> >
On 15.08.21 10:52, to...@tuxteam.de wrote:
On Sun, Aug 15, 2021 at 10:34:05AM +0200, Evelyn Pereira Souza wrote:
Hi
https://unix.stackexchange.com/questions/616926/debian-10-6-boots-to-black-screen-no-screens-foundee-in-log
same problem like this guy, but sadly no anser.
You also have a
* 2021-08-15 11:36:54+0200, Hans wrote:
> 2. deb http://security.debian.org/ stable/updates main contrib non-free
> is not reachable.
When upgrading a Debian system you should always read the release notes.
https://www.debian.org/releases/bullseye/amd64/release-notes/
Section 4.2.7 says:
On Sonntag, 15. August 2021 05:36:54 -04 Hans wrote:
> Dear list,
>
> since the release of bullseye I got into two issues.
>
> 1. the pgp-key of the repo are no more valid.
>
> Is there a new one? How to get?
>
> 2. deb http://security.debian.org/ stable/updates main contrib
> non-free is not
Dear list,
since the release of bullseye I got into two issues.
1. the pgp-key of the repo are no more valid.
Is there a new one? How to get?
2. deb http://security.debian.org/ stable/updates main contrib non-free
is not reachable.
Is it down? How can it be fixed?
Another thing besides
Hi.
On Sun, Aug 15, 2021 at 08:49:49AM +0200, to...@tuxteam.de wrote:
> On Sat, Aug 14, 2021 at 06:06:50PM -0400, Stefan Monnier wrote:
> > > Nevertheless there are rare cases only root can make changes.
> >
> > You mean cases where `sudo zsh -l` is not an option?
>
> Up to now, there
On 2021-08-15 10:46:16 +0200, Frank wrote:
> Op 15-08-2021 om 08:23 schreef John Covici:
> > Hi. I did a apt-get update changing from buster to bullseye and got
> > the above message -- should I just wait a few days and try again or
> > something else?
> >
> > Thanks.
> >
> bullseye/updates is
On Sun, Aug 15, 2021 at 10:34:05AM +0200, Evelyn Pereira Souza wrote:
> Hi
>
> https://unix.stackexchange.com/questions/616926/debian-10-6-boots-to-black-screen-no-screens-foundee-in-log
>
> same problem like this guy, but sadly no anser.
You also have a "2019 5k iMac"? Because that is very
On Sun, Aug 15, 2021 at 08:24:13AM +0200, john doe
wrote:
> The below assumes that 'sources.list' is set only for bullseye
>
> Some hints more than an answer:
> - Try to remove the gpg keys in '/etc/apt' directory.
> - Try to remove the Debian apt-keyring pkg ('$ apt-get --autoremove
> purge
Op 15-08-2021 om 08:23 schreef John Covici:
Hi. I did a apt-get update changing from buster to bullseye and got
the above message -- should I just wait a few days and try again or
something else?
Thanks.
bullseye/updates is not the location for bullseye's security repo.
Change the relevant
1 - 100 of 105 matches
Mail list logo
