Fix verified on 2024.2 version.
Thank you.
daniel.scati
@daniel.scati
Best posts made by daniel.scati
Latest posts made by daniel.scati
-
RE: GPG error updating Debian repositories
-
RE: Date in Debian feed release file malformed
Fix verified on 2024.2 version.
Thank you. -
Date in Debian feed release file malformed
Hi, I'm getting warnings about invalid date using Debian feeds when update from clients.
The specific error is the following:W: Invalid 'Date' entry in Release file /var/lib/apt/lists/neptuno.sisifo.this:8080_debian_test_dists_bionic_InRelease
The issue is that the release file generated by ProGet writes the Date in local format, not following the Debian guidelines:
The date has the following format 7 (compatible and with the same semantics of RFC 2822 and RFC 5322):
day-of-week, dd month yyyy hh:mm:ss +zzzz
where:
- day-of-week is one of: Mon, Tue, Wed, Thu, Fri, Sat, Sun
- dd is a one- or two-digit day of the month (01-31)
- month is one of: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec
- yyyy is the four-digit year (e.g. 2010)
- hh is the two-digit hour (00-23)
- mm is the two-digit minutes (00-59)
- ss is the two-digit seconds (00-60)
- +zzzz or -zzzz is the time zone offset from Coordinated
Executing a grep among the InRelease files I notice that the Date in ProGet release files is in Spanish format instead of English:
operador@scatipc:~$ grep Date /var/lib/apt/lists/*_InRelease /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_bionic_InRelease:Date: Thu, 26 Apr 2018 23:37:48 UTC /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_bionic-updates_InRelease:Date: Fri, 19 Apr 2024 1:22:01 UTC /var/lib/apt/lists/linux.teamviewer.com_deb_dists_stable_InRelease:Date: Tue, 23 Apr 2024 07:26:48 UTC /var/lib/apt/lists/neptuno.sisifo.this:8080_debian_test2_dists_bionic_InRelease:Date: vie., 19 abr. 2024 06:09:01 UTC /var/lib/apt/lists/neptuno.sisifo.this:8080_debian_test3_dists_bionic_InRelease:Date: jue., 25 abr. 2024 06:31:46 UTC /var/lib/apt/lists/neptuno.sisifo.this:8080_debian_test4_dists_bionic_InRelease:Date: jue., 25 abr. 2024 06:31:46 UTC /var/lib/apt/lists/neptuno.sisifo.this:8080_debian_test_dists_bionic_InRelease:Date: jue., 25 abr. 2024 06:31:45 UTC /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_bionic-security_InRelease:Date: Mon, 13 Nov 2023 0:36:15 UTC
I presume the problem is originated because my ProGet server runs in a Windows Server in Spanish language, otherwise many users would have reported it. But the Release generation should ignore any language format, using always the English standard to avoid those warnings in client computers.
Thank you.
-
RE: GPG error updating Debian repositories
@philippe-camelio_3885 thanks for the piece of advice about how to import the certificate on Jammy, but I already used that way, and it also fails.
After several tests I found out the root of the problem, and strange as it may seem, it is caused for the Description field in the Properties of Manage Feed. The feed description supports markdown format, but if it contains a break line with a blank line, after some minutes (or hours?) it will start to fail in the client when execute an update.
One example of a description that reproduce the bug could be:**Fabricaci贸n** Instaladores Ubuntu liberados a producci贸n
The second blank line is the one that causes the issue. Fortunately, edit the description removing the blank line solves it
-
RE: GPG error updating Debian repositories
Is there any documentation about how ProGet generate the certificates for Debian repositories? or, where I could find them in a Windows installation? To have something to start working with.
I tried searching for any file with .asc extension, but there is nothing found in my Windows installation, so I guess certificates like stable.asc are generated/stored somehow on the website for download 驴?I'm totally willing to help as far as I can. Thank you.
-
GPG error updating Debian repositories
Hi. I'm having troubles using debian repositories on Ubuntu.
I've followed the instructions to use the debian repository and the key was imported correctly, but when I run apt update command the following error appears:W: GPG error: https://myserver:8080/debian/stable jammy InRelease: The following signatures were invalid: BADSIG D263579579B65410 stable@proget E: The repository "https://myserver:8080/debian/stable jammy InRelease" is not signed.
I tried on Bionic and Jammy versions with several client computers. I tried importing the key with apt and using a keyring directory. I tried with different feeds. But the same error always appears.
How could I solve it? Is it any way to recreate the ".asc" keys? Maybe there is some kind of error with them.Thank you.
-
RE: Wrong debian apt documentation (web and app)
Setting aside the apt-key deprecation point. I'm using now 2023.32 and the Integrate with apt documentation is perfect now.
If I'm not wrong the web documentation it's still incorrect, though.Add the signing key To add the signing key to apt, run the following command: wget -qO - http://{proget-server}/debian/keys/{feed-name}.asc | sudo apt-key add -
Should be:
wget -qO - http://{proget-server}/debian/{feed-name}/keys/{feed-name}.asc | sudo apt-key add -
-
RE: Incorrect packages count in Feeds page
Just to give you a heads up. I'm already on version 2023.32 and it works like a charm.
Thank you. -
RE: Incorrect packages count in Feeds page
Nice!
I'll be waiting for the next release.
Thank you very much. -
Wrong debian apt documentation (web and app)
Hi,
I found several mistakes in the debian feeds client configuration documentation, both inedo docs webpage and proget app web (strangely they aren't the same).
https://docs.inedo.com/docs/proget-feeds-debian
wget -qO - http://{proget-server}/debian-feeds/keys/{feed-name}.asc
In a new Debian feed that URL address return the error (404) Not Found.In the section Adding the repository there is a misspelling (debina vs debian)
echo "deb http://{proget-server}/debina/{feed-name} {distro-name} {component-name}"
On the other side the information the Integrate with apt information on proget web app is also erroneous:
echo "deb http://myserver:8624/debian/stable/bionic libs scati third" | sudo tee "/etc/apt/sources.list.d/proget-stable.list"
The distro-name should be separated by a space from the URLecho "deb http://myserver:8624/debian/stable bionic libs scati third"
Above all, bear in mind that apt-key was considered deprecated as of Debian 11 and Ubuntu 22.04