Re: Instalacja Debian8 błąd w Release

[Anders Andersson]

On Thu, Jan 13, 2022 at 3:13 PM piorunz  wrote:
>
> Witaj Wojciech,
>
> On 13/01/2022 11:02, Wojciech wrote:
> >
> > Kiedy mogę się spodziewać naprawienia ?
>
> Never. Jessie end of life was in June 2018, and LTS support has ended in
> June 2020, one and half years ago. It's a surprise that some Jessie
> packages are even available online somewhere. This is not guaranteed.

I would be more surprised if the packages were *not* available
somewhere, and I hope they are "guaranteed" the same way as the new
packages (that is, no guarantee other than the benevolence of the
community members). These things are very important for current and
future "software archeology" and for preserving the history and
evolution of computing.

Heck, I even had to install Debian Sarge a few years ago to try to
figure out how a very old piece of software was supposed to be built.
It was neat to have the whole ecosystem as a 2005 developer expected
and I'm very happy that the old versions were still downloadable!

Re: OT: Recommendation for a new Debian laptop

[john doe]

On 1/12/2022 9:29 AM, Jeremy Ardley wrote:


On 12/1/22 4:12 pm, Jeremy Ardley wrote:



The only requirement is to have virtualisation available.


My advice is if you are going to be doing any virtual work is get a
laptop with

- decent processor ( I use Ryzen mid range )

- Expandable memory to 32G

- NVME PCIe system drive (256G upwards)

- Large internal secondary drive - typically SATA 1G +

In terms of things just working nicely, I prefer ASUS, but most brands
with those specs will be able to do all you want.

Standard off the shelf systems are either very expensive or don't have
the memory and disk you will need.

Get the cheapest one with the capabilities needed and do the upgrades
yourself for usually a lot cheaper

--

Jeremy


Typical laptops off the shelf offer 8G ram, 256G drive (beware of SATA
instead of preferred PCIe) and if you are lucky a 1T SATA secondary HDD
(mistake in previous post 1T not 1G).

Check the specs on these to see how much RAM you can upgrade to. 32G or
better is what you want.

And always get a good CPU to start with. Ryzen 5 is very workable.




I've looked a bit online and laptops with a Ryzen CPU (5 .../7 ...) are
between 550 and 1000 box or more.
is this price range what you were suggesting?

IN other words, if you were to buy a new laptop which one would you pick.


Thanks all for the model suggestions and ensuring that KVM support is
available.

--
John Doe

Re: ssl certificate files?

[tomas]

On Fri, Jan 14, 2022 at 08:24:51PM -0500, Karen Lewellen wrote:
> Hi folks,
> In an effort to be part of the solution for  my shell service provider, I
> have a question.
> We are getting ssl certificate not trusted errors,  which I understand post
> issues at the end of November, can be corrected with new ssl certificate
> files.
> main issue is in lynx  2.9.dev5
> where there is a place to provide the ssl key file name.
> Any good sources for them?

Karen,

I don't quite understand what you are up to. Some context seems missing:
what application is complaining about a non-trusted certificate? What
application is providing it? Where did you (or your provider) get this
(not trusted) certificate from?

You say lynx: that seems to be the client complaining. So I assume (am I
right?) the server providing the certificate might be a Web server
(Apache?). Does the error happen with another client? (e.g. Firefox).

This is relevant because, apparently, some clients actively fetch
missing intermediate certificates (FF, for one), some don't, so the
latter have to be fed a complete cert chain up to a trusted root.

Lastly, you mention "...to provide the ssl key file name". To whom? To
the (I'm making that up, see above) server? This is server configuration,
so it will depend on what server. If it's Apache (not necessarily the
best choice, mind you, but probably the most widespread), here [1] is
some documentation to get you started.

The whole topic is somewhat involved, and I don't know what you know and
what not, so it might take some back-and-forth. Just ask away!

Cheers

[1] https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html

-- 
t


signature.asc
Description: PGP signature

Re: Bullseye Installer Fails to find soundcard

[john doe]

On 1/15/2022 6:04 AM, David J. J. Ring, Jr. wrote:

I'm just a user.  I've been trying to install Bullseye since the Release 
Candidates, no luck.

The accessible text installer fails to find my sound card.  I think my sound 
card is the
second one that Debian finds, so I select that.

I do get sound in console once installed, but a blind person would not be able 
to install
as there is no sound, unless they had a braille device.

I've contacted debian-accessibility and debian-boot, but I just don't know 
where the problem
is, Samual from debian-accessibility says it's alsa, but I'm not a programmer, 
or developer, I'm
just a user.

I've spent hundreds of hours trying to install Debian Bullseye.  The last 
release of Debian Buster
installs perfectly, it detects my sound card, I have sound during installation, 
and upon reboot.

But suddenly in Debian Bullseye, something has changed. No sound during 
accessible text installtion.

I don't know who to report this bug to.



Looks like a ticket is already opened 'Re: Bug#1002976:
installation-reports: Installer Fault Accessibility No Screen Reader Heard'.

This thread is also on the debian-accessibility and the debian-boot lists.

--
John Doe

Re: Bullseye Installer Fails to find soundcard

[Jude DaShiell]

If the first possible port is hdmi it could be debian is getting hung up
on that port and thinks it's your default port.  This is not a new
problem.  Maybe a -nohdmi boot parameter could be added to instruct the
installer to bypass all of those hdmi ports if that's the problem you're
having.  If you have an hdmi connection possible with your video monitor
and this again is an hdmi problem maybe plugging a monitor into that hdmi
port might solve the problem.


On Sat, 15 Jan 2022, David J. J. Ring, Jr. wrote:

> I'm just a user.  I've been trying to install Bullseye since the Release 
> Candidates, no luck.
>
> The accessible text installer fails to find my sound card.  I think my sound 
> card is the
> second one that Debian finds, so I select that.
>
> I do get sound in console once installed, but a blind person would not be 
> able to install
> as there is no sound, unless they had a braille device.
>
> I've contacted debian-accessibility and debian-boot, but I just don't know 
> where the problem
> is, Samual from debian-accessibility says it's alsa, but I'm not a 
> programmer, or developer, I'm
> just a user.
>
> I've spent hundreds of hours trying to install Debian Bullseye.  The last 
> release of Debian Buster
> installs perfectly, it detects my sound card, I have sound during 
> installation, and upon reboot.
>
> But suddenly in Debian Bullseye, something has changed. No sound during 
> accessible text installtion.
>
> I don't know who to report this bug to.
>
> Best wishes,
>
> David
>

Bullseye Installer Fails to find soundcard

[David J. J. Ring, Jr.]

I'm just a user.  I've been trying to install Bullseye since the Release 
Candidates, no luck.

The accessible text installer fails to find my sound card.  I think my sound 
card is the 
second one that Debian finds, so I select that.

I do get sound in console once installed, but a blind person would not be able 
to install
as there is no sound, unless they had a braille device.

I've contacted debian-accessibility and debian-boot, but I just don't know 
where the problem
is, Samual from debian-accessibility says it's alsa, but I'm not a programmer, 
or developer, I'm
just a user.

I've spent hundreds of hours trying to install Debian Bullseye.  The last 
release of Debian Buster
installs perfectly, it detects my sound card, I have sound during installation, 
and upon reboot.

But suddenly in Debian Bullseye, something has changed. No sound during 
accessible text installtion.

I don't know who to report this bug to.

Best wishes,

David


signature.asc
Description: PGP signature

ssl certificate files?

[Karen Lewellen]

Hi folks,
In an effort to be part of the solution for  my shell service provider, I 
have a question.
We are getting ssl certificate not trusted errors,  which I understand 
post issues at the end of November, can be corrected with new ssl 
certificate files.

main issue is in lynx  2.9.dev5
where there is a place to provide the ssl key file name.
Any good sources for them?
Thanks,
Karen

Re: OT: anybody uses eero 6 WiFi router?

[Alexander V. Makartsev]

On 14.01.2022 19:02, Anssi Saari wrote:

"Alexander V. Makartsev"  writes:


If I was in the market for the router for myself, I'd always choose
one from MikroTik¹.
They all have no-nonsence hardware and software design...

I can't agree with the software part. Or I guess no-nonsense can be
agreed but I just find their web config interface messy,
counter-intuitive and poorly documented.
It is probably because nobody needs or uses it. WinBox and CLI-over-SSH 
are the way to go.
Cisco devices don't have very comfortable Web-GUI either and I can't 
really imagine a web interface that
will be able to manage these kind of devices with this level of 
complexity and look fancy and be secure at the same time.



Same goes for their proprietary
CLI. And they provide their own awful script language too.
I'll choose RouterOS CLI over IOS CLI any time of a day. It's really a 
matter of personal preference.
Tab-completion\suggestion of ROS CLI really helps to get around and do 
the job.
I also think, any CLI is made for scripting first and manual management 
second.

I do use it on occasion when I inevitably screw something up.


Mikrotik's HW seems fine and they have a reputation for reliability
although my hEX S runs rather hot.


The only downside I can think of is somewhat advanced configuration
could be difficult for somebody, but with help from official forum and
wiki² quite manageable and as a bonus I'll learn a lot about
networking, routing.

That downside is huge. The thing is, I already know a lot about
networking and routing. What I don't know is all the Mikrotik
proprietary stuff or "the Mikrotik way". And since it all seems kind of
ass-backwards I don't particularly want to learn.
I couldn't find any "the Mikrotik way" things. Proprietary probably, but 
I think it is just a Linux (BSD?) kernel, that was

highly optimized performance-wise for variety of different architectures.
When I think about it all I see is just interfaces of different kind¹, 
L2 and L3 packet filter² and various tools to watch, debug and monitor 
traffic.
Anything you'd find in there will have an existing RFC and all of it 
build up on the same algorithms you find in Linux.



For sure, most router makers seem to think they have to add a fat
proprietary layer of crap on top of Linux. I have recent experience from
a Draytek router but at least their web interface was easily understood
even if things were placed strangely and some things were just odd. Too
bad the router didn't actually work reliably enough so I RMAd it and got
the Mikrotik.
Once again, a matter of preference. I guess some people just want a 
fancy GUI dashboard to look at.
MikroTik is like C. It's low-level, really fast and powerful, but you 
have to know how to use it. :)



Anyways, as soon as I have some free time I'll be setting up my PC
Engines APU2 board with Debian Linux to act as my router.

I will be delighted to see a screen shot of a web interface you made for it.
I also yet to see an SMB-grade feature-wise router for the price of a 
SOHO-grade one.




¹ Bridges, VLANs, Bonding, PPP, etc, configured in the same way you 
would do it on Linux, but without cryptic config lines,
   where you have to verify every word you type with a man page, 
sometimes more than once.
² Judging by the way it looks and works is probably a carbon copy of 
iptables+ebtables with existing extensions.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Instalacja Debian8 błąd w Release

[Georgi Naplatanov]

On 1/14/22 18:56, Wojciech wrote:
> Thanks Georgi.
> 
> Guys, Don't solve it. I solved it myself.
> I have a feeling you don't quite understand what I'm writing about.
> 
> choose-mirror pointing to the branch
> http://ftp.pl.debian.org/debian/dists/jessie/
> The Release found there points (redirects) to
> http://ftp.pl.debian.org/debian/dists/oldoldstable/
> At that location lies another distribution/different version, not Jessie.
> This pointing is wrong regardless of whether Jessie is oldoldstable or
> should be archive.
> Jessie is not in the indicated/redirected
> http://ftp.pl.debian.org/debian/dists/oldoldstable/. There is a
> different version there.
> 
> Of course i soo https://www.debian.org/distrib/archive, but in this
> pleaces isn't Jessie (Debian 8). The latest version is squeeze (Debian 6).
> Of course i don't why. In my opinion Debian 8 should be moved to
> archive, but it is not

Hi Wojciech,

on that page are listed all Debian archive mirrors.

https://www.debian.org/distrib/archive

If you pickup the first mirror you'll see that Debian Jessie is there

http://archive.debian.org/debian-archive/debian/dists/

Kind regards
Georgi

Re: Instalacja Debian8 błąd w Release

[Greg Wooledge]

On Fri, Jan 14, 2022 at 05:56:19PM +0100, Wojciech wrote:
> choose-mirror pointing to the branch
> http://ftp.pl.debian.org/debian/dists/jessie/
> The Release found there points (redirects) to
> http://ftp.pl.debian.org/debian/dists/oldoldstable/
> At that location lies another distribution/different version, not Jessie.

So, this mirror is broken?  Then use a different mirror.

Unless there's a need to use a very specific mirror, it's recommended
to use the deb.debian.org infrastructure.  For jessie, according to the
wiki, the last known good sources.list entries are:

deb http://deb.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main

Re: Instalacja Debian8 błąd w Release

[Wojciech]

Thanks Georgi.

Guys, Don't solve it. I solved it myself.
I have a feeling you don't quite understand what I'm writing about.

choose-mirror pointing to the branch 
http://ftp.pl.debian.org/debian/dists/jessie/
The Release found there points (redirects) to 
http://ftp.pl.debian.org/debian/dists/oldoldstable/

At that location lies another distribution/different version, not Jessie.
This pointing is wrong regardless of whether Jessie is oldoldstable or 
should be archive.
Jessie is not in the indicated/redirected 
http://ftp.pl.debian.org/debian/dists/oldoldstable/. There is a 
different version there.


Of course i soo https://www.debian.org/distrib/archive, but in this 
pleaces isn't Jessie (Debian 8). The latest version is squeeze (Debian 6).
Of course i don't why. In my opinion Debian 8 should be moved to 
archive, but it is not


Regards and nice to day.
Wojciech

In Polish- Georgi, Perhaps my English isn't very well , it isn't 
understandable. Please, if it is necessary, correct translate.


Chłopaki, nie rozwiązujcie tego. Sam to rozwiązałem.
Mam wrażenie, że nie do końca rozumiecie o czym piszę.
choose-mirror wskazujący na gałąź 
http://ftp.pl.debian.org/debian/dists/jessie/
Znaleziony tam Release wskazuje (przekierowuje) na 
http://ftp.pl.debian.org/debian/dists/oldoldstable/

W tej lokalizacji leży inna dystrybucja/wersja, nie Jessie.
Takie wskazanie jest błędne niezależnie od tego, czy Jessie jest 
oldoldstable, czy powinna być archiwalna.
Jessie nie znajduje się we wskazanym/przekierowanym 
http://ftp.pl.debian.org/debian/dists/oldoldstable/. Jest tam inna wersja.


Oczywiście widziałem https://www.debian.org/distrib/archive, ale w tym 
miejscu/stronie nie ma Jessie (Debian 8). Najnowsza wersja to squeeze 
(Debian 6).
Oczywiście nie wiem czemu. W mojej opini Debian 8 winien być 
przeniesiony do archiwum, ale tak nie jest.


Pozdrawiam i życzę miłego dnia.
Wojciech

Przetłumaczono z www.DeepL.com/Translator (wersja darmowa)

W dniu 14.01.2022 o 11:51, piorunz pisze:

Tu masz rozwiazanko :)

Hi Wojciech,

for old unsupported versions of Debian you should not use regular Debian
mirrors, you should use "archive" mirrors.

https://www.debian.org/distrib/archive

Kind regards
Georgi

Re: restructure folders

[Jonathan Dowland]

On Thu, Jan 13, 2022 at 07:23:14AM -0500, Greg Wooledge wrote:

First of all, this already exists:

https://manpages.debian.org/


Alas OP mentioned (not in the top message) that this is for an offline
system.

However manpages.d.o mentions it is generated using this software:

https://github.com/Debian/debiman

OP could give that a try.

Another option would be to contact the manpages.d.o maintainers and
discuss mirroring (or at least downloading) all of the generated data.
See  for who to get in touch with.

--
Please do not CC me for listmail.

👱🏻  Jonathan Dowland
✎j...@debian.org
🔗   https://jmtd.net

Re: Why do experimental packages (e.g. clang-13) get in unstable?

[Jonathan Dowland]

On Fri, Jan 14, 2022 at 10:56:19AM +0100, Vincent Lefevre wrote:

So clang-13 1:13.0.1~+rc1-1~exp4 testing is in testing/unstable,
but the changelog says:

llvm-toolchain-13 (1:13.0.1~+rc1-1~exp4) experimental; urgency=medium


Because despite what the changelog or the version string say, the
maintainer uploaded that version to unstable:

https://tracker.debian.org/news/1293514/accepted-llvm-toolchain-13-11301rc1-1exp4-source-into-unstable/



--
Please do not CC me for listmail.

👱🏻  Jonathan Dowland
✎j...@debian.org
🔗   https://jmtd.net

python-apt create_pin question

[Antonio Russo]

Hello!

I'm trying to use apt_pkg to get a "best candidate" for a package, but with
slightly different constraints than I have set up in /etc/apt/preferences.d.

I am trying to use Policy.create_pin to do so, but cannot seem to get it 
working:

import apt_pkg

apt_pkg.init()
cache = apt_pkg.Cache(progress=None)
policy = apt_pkg.Policy(cache)
#policy.create_pin('origin', '', 'Debian', -1)
policy.create_pin('origin', 'apt', 'Debian', -1)
policy.init_defaults()

print([ (v, policy.get_priority(v)) for v in cache['apt'].version_list ])


All calls to get_priority return 500---not -1, as I am trying to get here.

I must be doing something silly.  I'd appreciate any help.

Best,
Antonio

Re: OT: anybody uses eero 6 WiFi router?

[Dan Ritter]

Anssi Saari wrote: 
> For sure, most router makers seem to think they have to add a fat
> proprietary layer of crap on top of Linux. I have recent experience from
> a Draytek router but at least their web interface was easily understood
> even if things were placed strangely and some things were just odd. Too
> bad the router didn't actually work reliably enough so I RMAd it and got
> the Mikrotik.
> 
> Anyways, as soon as I have some free time I'll be setting up my PC
> Engines APU2 board with Debian Linux to act as my router.

This is an excellent way to go.

My low-power AMD Kabrini has been serving as a router running
Debian since 2014.

-dsr-

Re: OT: anybody uses eero 6 WiFi router?

[Anssi Saari]

"Alexander V. Makartsev"  writes:

> If I was in the market for the router for myself, I'd always choose
> one from MikroTik¹.

> They all have no-nonsence hardware and software design...

I can't agree with the software part. Or I guess no-nonsense can be
agreed but I just find their web config interface messy,
counter-intuitive and poorly documented. Same goes for their proprietary
CLI. And they provide their own awful script language too.

Mikrotik's HW seems fine and they have a reputation for reliability
although my hEX S runs rather hot.

> The only downside I can think of is somewhat advanced configuration
> could be difficult for somebody, but with help from official forum and
> wiki² quite manageable and as a bonus I'll learn a lot about
> networking, routing.

That downside is huge. The thing is, I already know a lot about
networking and routing. What I don't know is all the Mikrotik
proprietary stuff or "the Mikrotik way". And since it all seems kind of
ass-backwards I don't particularly want to learn.

For sure, most router makers seem to think they have to add a fat
proprietary layer of crap on top of Linux. I have recent experience from
a Draytek router but at least their web interface was easily understood
even if things were placed strangely and some things were just odd. Too
bad the router didn't actually work reliably enough so I RMAd it and got
the Mikrotik.

Anyways, as soon as I have some free time I'll be setting up my PC
Engines APU2 board with Debian Linux to act as my router.

Re: Installation Debian8 error in Release

[Georgi Naplatanov]

On 1/14/22 03:16, Wojciech wrote:
> Hi,
> Thanks Tomas for your answer.
> In the installation process, at the moment of when I choosing mirror
> server for example  http://ftp.pl.debian.org/debian/dist/jessie/Release
> installation is break.
> For jessie is selected choose-mirror: wget -q
> http://ftp.pl.debian.org/debian/dist/jessie/Release -O - | grep -E 
> '^(Suite|Codename):'
> Output this command is:
> Suite:  oldoldstable
> Codename: jessie
> In the next step is choose-mirror: wget -q
> http://ftp.pl.debian.org/debian/dist/oldoldstable/Release -O - | grep -E
> '^(Suite|Codename):' because earlier Suite is oldoldstable (2xold and
> stable)
> Output this command is:
> Suite: oldoldstable
> Codename: stretch
> Attention: not jessie
> 
> Codename jessie is version 8.11
> Codename stretch is version 9.11
> 
> Correct destination link is oldoldoldstable (3xold and stable)
> Realease from http://ftp.pl.debian.org/debian/dists/oldoldoldstable/Release:
> "
> Origin: Debian
> Label: Debian
> Suite: oldoldstable
> Version: 8.11
> Codename: jessie
> ..."
> Correct entry in   http://ftp.pl.debian.org/debian/dists/jessie/Release
> will be
> "
> Origin: Debian
> Label: Debian
> Suite: oldoldoldstable
> Version: 8.11
> Codename: jessie
> ..."
> This situation is on many mirror servers. I checked Sweden, Switzerland,
> Holland and USA.
> Is it a little clearer now ?
> Workaround this trouble is installation without mirror server, and after
> reboot write manually list source packages to /etc/apt/sources.list and
> run tasksel and choose components (of course after apt update)
> 
> Have a nice day
> 
> W dniu 13.01.2022 o 14:58, Thomas Schmitt pisze:
>> Hi,
>>
>> Google translation says that Wojciech wrote:
>>> During the installation, when you choose a mirror server, packages is
>>> mistake.
>> Maybe the fallback servers listed in debian-8.11.1-amd64-DVD-1.jigdo
>> can be used.
>> I understand that this one is quite time specific:
>>
>>   http://snapshot.debian.org/archive/debian/20190212T020859Z/
>>
>> (But its libburn versions date back to 2012.)
>>
>> This one seems to be the last resort for everything ever released:
>>
>>   http://us.cdimage.debian.org/cdimage/snapshot/Debian/
>>
>>
>>> Is this email enough if I have to write to a world group?
>> It would be better in english language.
>> Google translations tend to become riddling or ridiculous.


Hi Wojciech,

for old unsupported versions of Debian you should not use regular Debian
mirrors, you should use "archive" mirrors.

https://www.debian.org/distrib/archive

Kind regards
Georgi

Why do experimental packages (e.g. clang-13) get in unstable?

[Vincent Lefevre]

Hi,

zira:~> apt-show-versions -a clang-13
clang-13:amd64 1:13.0.0-9+b2 install ok installed
No stable version
No stable-updates version
clang-13:amd64 1:13.0.1~+rc1-1~exp4 testing  ftp.debian.org
clang-13:amd64 1:13.0.1~+rc1-1~exp4 unstable ftp.debian.org
clang-13:amd64 1:13.0.1~+rc2-1~exp1 experimental ftp.debian.org
clang-13:amd64/testing 1:13.0.0-9+b2 upgradeable to 1:13.0.1~+rc1-1~exp4

So clang-13 1:13.0.1~+rc1-1~exp4 testing is in testing/unstable,
but the changelog says:

llvm-toolchain-13 (1:13.0.1~+rc1-1~exp4) experimental; urgency=medium

  * Fix the cmake file with the mlir introducing

 -- Sylvestre Ledru   Thu, 06 Jan 2022 14:30:59 +0100
[...]

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)