41

Software - Support / Re: [Solved] How to migrate sources.list entries to deb822?

« Last post by onepiece on 2025/01/23, 22:05:44 »

Guess its been [Solved]  for everybody but me...   
I still dont get how all these pieces are supposed to fit.

I'll crawl back into my cave till I do a future Siduction re-install. 
At that time hope the details on this deb822 format conversion are automatically carried out at install time.

Best to all.

42

Software - Support / Re: [Solved] How to migrate sources.list entries to deb822?

« Last post by ruebe99 on 2025/01/23, 21:57:02 »

no idea were to find your probs. I get on that machine

inxi -r | grep -v "No active apt repos in:"
Repos:
  Active apt repos in: /etc/apt/sources.list.d/aptosid.list
    1: deb [signed-by=/usr/share/aptosid-archive-keyring/aptosid-archive-keyring.gpg] http://aptosid.com/debian/ sid main fix.main
  Active apt repos in: /etc/apt/sources.list.d/archive_uri-http_www_deb-multimedia_org-trixie.list
    1: deb [signed-by=/etc/apt/trusted.gpg.d/deb-multimedia-keyring.gpg] http://www.deb-multimedia.org/ testing non-free main
  Active apt repos in: /etc/apt/sources.list.d/backports.list
    1: deb [signed-by=/usr/share/keyrings/backports-archive-keyring.gpg] http://deb.debian.org/debian/ trixie-backports main contrib
  Active apt repos in: /etc/apt/sources.list.d/codecs.list
    1: deb [signed-by=/usr/share/keyrings/codecs-archive-keyring.gpg] http://ftp.debian.org/debian/ bullseye-backports main non-free
    2: deb [signed-by=/usr/share/keyrings/codecs-archive-keyring.gpg] http://ftp.debian.org/debian/ bookworm-backports main non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] http://httpredir.debian.org/debian/ sid main contrib non-free non-free-firmware
    2: deb [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] http://httpredir.debian.org/debian/ testing main contrib non-free non-free-firmware
    3: deb-src [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] http://httpredir.debian.org/debian/ sid main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/extra.list
    1: deb [signed-by=/usr/share/siduction-archive-keyring/siduction-archive-keyring.gpg] https://packages.siduction.org/extra unstable main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/fixes.list
    1: deb [signed-by=/usr/share/siduction-archive-keyring/siduction-archive-keyring.gpg] https://packages.siduction.org/fixes unstable main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/google-chrome-archive-keyring.gpg] http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/openproject.list
    1: deb [signed-by=/usr/share/keyrings/openproject-archive-keyring.gpg] https://dl.packager.io/srv/deb/opf/openproject/stable/12/debian/ 10 main
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt/ xenial main
  Active apt repos in: /etc/apt/sources.list.d/sublime-text.list
    1: deb [signed-by=/usr/share/keyrings/sublime-text-archive-keyring.gpg] https://download.sublimetext.com/ apt/stable/
  Active apt repos in: /etc/apt/sources.list.d/winehq.list
    1: deb [signed-by=/usr/share/keyrings/winehq-archive-keyring.gpg] https://dl.winehq.org/wine-builds/debian/ bullseye main

sorry, but everything works fine for my tiny little installation.
what contradicts the
https://gist.github.com/maxhq/7dadf55064aaadc4d9e5993f89fad7b0
( migrate-apt-keys.sh  )

ruebe99

43

Upgrade Warnings / Re: Python 3 upgrade forces removal of hplip & friends

« Last post by dibl on 2025/01/23, 21:23:02 »

...
But if I may ask for a favor, as a member of the siduction community board you are in a much better position to suggest to the authors of hplip ...

I am flattered to be considered such a strong influencer, and I am willing to do anything I can to help the community.

However, we learned from the bug report in post #8 up this thread, the Debian Printing Team has been asleep since 9 JUL 2024, regarding the last bug reported. So, I don't see a way to wake them up with another report, or other way. Do you have an idea how to do it?

44

Software - Support / Re: [Solved] How to migrate sources.list entries to deb822?

« Last post by hendrikL on 2025/01/23, 21:22:04 »

Please, take a look to the signed-by line.

And  for the record, debian and siduction a two different things.

So you need a debian sources and a fixes. sources and a extra sources,

45

Software - Support / Re: How to migrate sources.list entries to deb822?

« Last post by eriefisher on 2025/01/23, 21:14:24 »

Hello Folks,
Onepiece here.  I made Reply #2 on this tread.
I have an understanding of the theory of what needs to be done to fix this, but I'm still very, very  confused about the actual steps needed to remedy.  There are some highly experienced and highly technical answers in this thread, but I'm hoping someone can "dumb it down" for me to do the fix.  Here is my understanding...please correct me where I'm off track.

The old way of managing “Signed by” is using the standard file that was created during the initial installation.  This now outdated file is called:  /etc/apt/sources.list. 
This file should be DELETED and REPLACED by the new deb822 format-compliant file titled:   /etc/apt/sources.list.d/debian.sources

The contents of the new file, /etc/apt/sources.list.d/debian.sources should contain a short paragraph for EACH of the Notices that indicate a Signed by problem.  In my case these Notices are:

          Notice: Missing Signed-By in the sources.list(5) entry for 'https://deb.debian.org/debian
          Notice: Missing Signed-By in the sources.list(5) entry for 'https://packages.siduction.org/fixes'

So, I should create a new /etc/apt/sources.list.d/debian.sources file that contains these two paragraphs:

Types:      deb
 URIs:       https://deb.debian.org/debian/
 Suites:     unstable
 Components: main contrib non-free non-free-firmware
 Enabled:    yes
 Signed-By:  /usr/share/keyrings/debian-archive-keyring.gpg


Types:      deb
 URIs:       https://packages.siduction.org/fixes
 Suites:     unstable
 Components: main contrib non-free non-free-firmware
 Enabled:    yes
 Signed-By:  /usr/share/keyrings/debian-archive-keyring.gpg

Did I get this right?   Please dumb down any replies so that even a cave man can understand.  Thank you.
.
.

If you run apt update it will tell you if and what the problem is should you make a mistake creating the .sources file. The information is the same as the .list file. just the format has changed.

46

Software - Support / Re: How to migrate sources.list entries to deb822?

« Last post by micspabo on 2025/01/23, 20:56:51 »

Please compare extra.sources and fixes.sources from @hendrikL, especially the lines with "Components:"!
He only puts "main" into that line.

I do expect that its enough if "non-free" and "non-free-firmware" are placed in "debian.sources".

Code: [Select]

# inxi -r | grep -v "No active apt repos in:"
Repos:
  Active apt repos in: /etc/apt/sources.list.d/debian.sources
    1: deb https://deb.debian.org/debian/ unstable main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/extra.sources
    1: deb https://packages.siduction.org/extra unstable main
  Active apt repos in: /etc/apt/sources.list.d/fixes.sources
    1: deb https://packages.siduction.org/fixes unstable main

@hendrikL: Thanks a lot.

47

Software - Support / Re: How to migrate sources.list entries to deb822?

« Last post by onepiece on 2025/01/23, 20:38:00 »

Hello Folks,
Onepiece here.  I made Reply #2 on this tread.
I have an understanding of the theory of what needs to be done to fix this, but I'm still very, very  confused about the actual steps needed to remedy.  There are some highly experienced and highly technical answers in this thread, but I'm hoping someone can "dumb it down" for me to do the fix.  Here is my understanding...please correct me where I'm off track.

The old way of managing “Signed by” is using the standard file that was created during the initial installation.  This now outdated file is called:  /etc/apt/sources.list. 
This file should be DELETED and REPLACED by the new deb822 format-compliant file titled:   /etc/apt/sources.list.d/debian.sources

The contents of the new file, /etc/apt/sources.list.d/debian.sources should contain a short paragraph for EACH of the Notices that indicate a Signed by problem.  In my case these Notices are:

          Notice: Missing Signed-By in the sources.list(5) entry for 'https://deb.debian.org/debian
          Notice: Missing Signed-By in the sources.list(5) entry for 'https://packages.siduction.org/fixes'

So, I should create a new /etc/apt/sources.list.d/debian.sources file that contains these two paragraphs:

Types:      deb
 URIs:       https://deb.debian.org/debian/
 Suites:     unstable
 Components: main contrib non-free non-free-firmware
 Enabled:    yes
 Signed-By:  /usr/share/keyrings/debian-archive-keyring.gpg


Types:      deb
 URIs:       https://packages.siduction.org/fixes
 Suites:     unstable
 Components: main contrib non-free non-free-firmware
 Enabled:    yes
 Signed-By:  /usr/share/keyrings/debian-archive-keyring.gpg

Did I get this right?   Please dumb down any replies so that even a cave man can understand.  Thank you.
.
.

48

Upgrade Warnings / Re: [HINWEIS] apt update heute mit 'Notice' (DEB822-Format incoming ?)

« Last post by Isegrimm666 on 2025/01/23, 19:51:23 »

https://forum.siduction.org/index.php?topic=9606.0

Recht herzlichen Dank

(Ich hab ihn vorhin echt nicht gefunden)

49

Upgrade Warnings / Re: [HINWEIS] apt update heute mit 'Notice' (DEB822-Format incoming ?)

« Last post by hendrikL on 2025/01/23, 19:42:03 »

https://forum.siduction.org/index.php?topic=9606.0

50

Upgrade Warnings / Re: [HINWEIS] apt update heute mit 'Notice' (DEB822-Format incoming ?)

« Last post by Isegrimm666 on 2025/01/23, 19:23:26 »

Den Thread hatte ich in der Suche nicht gefunden, sorry.

('ne Verlinkung auf den Thread wäre jetzt nicht schlecht gewesen)