Repository für 16.04?

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Ich danke dir für die schnelle Hilfe. Es fehlt aber scheinbar für die Repo noch die Release-File.

      Source Code

      1. padrio@openmind:~$ sudo apt update
      2. Hit:1 http://mirror.hetzner.de/ubuntu/packages xenial InRelease
      3. Get:2 http://mirror.hetzner.de/ubuntu/packages xenial-backports InRelease [92.2 kB]
      4. Hit:3 http://mirror.hetzner.de/ubuntu/packages xenial-updates InRelease
      5. Get:4 http://mirror.hetzner.de/ubuntu/security xenial-security InRelease [94.5 kB]
      6. Hit:5 http://de.archive.ubuntu.com/ubuntu xenial InRelease
      7. Hit:6 http://security.ubuntu.com/ubuntu xenial-security InRelease
      8. Hit:7 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
      9. Hit:8 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
      10. Hit:9 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
      11. Ign:10 https://download.bloonix.de/repos/ubuntu xenial InRelease
      12. Err:11 https://download.bloonix.de/repos/ubuntu xenial Release
      13. 404 Not Found
      14. Reading package lists... Done
      15. E: The repository 'https://download.bloonix.de/repos/ubuntu xenial Release' does not have a Release file.
      16. N: Updating from such a repository can't be done securely, and is therefore disabled by default.
      17. N: See apt-secure(8) manpage for repository creation and user configuration details.
      18. padrio@openmind:~$
      Display All
    • Source Code

      1. padrio@openmind:~$ sudo apt-get update
      2. Hit:1 http://mirror.hetzner.de/ubuntu/packages xenial InRelease
      3. Get:2 http://mirror.hetzner.de/ubuntu/packages xenial-backports InRelease [92.2 kB]
      4. Hit:3 http://mirror.hetzner.de/ubuntu/packages xenial-updates InRelease
      5. Get:4 http://mirror.hetzner.de/ubuntu/security xenial-security InRelease [94.5 kB]
      6. Hit:5 http://de.archive.ubuntu.com/ubuntu xenial InRelease
      7. Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
      8. Get:7 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
      9. Hit:8 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
      10. Hit:9 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
      11. Ign:10 https://download.bloonix.de/repos/ubuntu xenial InRelease
      12. Hit:11 https://download.bloonix.de/repos/ubuntu xenial Release
      13. Fetched 281 kB in 0s (725 kB/s)
      14. Reading package lists... Done
      15. W: https://download.bloonix.de/repos/ubuntu/dists/xenial/Release.gpg: Signature by key 31A86A255B0E516B0C49AE661CD8BB07F120EC73 uses weak digest algorithm (SHA1)
      16. W: Invalid 'Date' entry in Release file /var/lib/apt/lists/download.bloonix.de_repos_ubuntu_dists_xenial_Release
      Display All


      Brauchst du vielleicht eine Ubuntu 16.04 Maschine zum testen?

      The post was edited 2 times, last by Padrio ().

    • Hast du es mal mit dem Jessie Repo probiert?

      Sehe es gerade...

      Source Code

      1. Reading package lists... Done
      2. W: https://download.bloonix.de/repos/debian/dists/jessie/Release.gpg: Signature by key 31A86A255B0E516B0C49AE661CD8BB07F120EC73 uses weak digest algorithm (SHA1)
      3. W: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/download.bloonix.de_repos_debian_dists_jessie_Release

    • Hey, ich würde mich hier gerne einhängen. Wäre es möglich das du noch ein Repo für arm64 hinzufügst ;) ?

      Source Code

      1. N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://download.bloonix.de/repos/ubuntu xenial InRelease' doesn't support architecture 'arm64'


      Hab hier nen Odroid C2 liegen, der würde das brauchen ^^.
    • Das Repo für Xenial ist leider wieder defekt.

      Source Code

      1. # cat /etc/apt/sources.list.d/bloonix.list
      2. deb https://download.bloonix.de/repos/ubuntu/ xenial main
      3. # apt-get update
      4. Hit:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
      5. Get:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
      6. Get:3 http://de.archive.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
      7. Hit:4 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
      8. Ign:5 https://download.bloonix.de/repos/ubuntu xenial InRelease
      9. Hit:6 https://download.bloonix.de/repos/ubuntu xenial Release
      10. Fetched 204 kB in 0s (296 kB/s)
      11. Reading package lists... Done
      12. W: Invalid 'Date' entry in Release file /var/lib/apt/lists/download.bloonix.de_repos_ubuntu_dists_xenial_Release
      13. # grep -r ^Date /var/lib/apt/lists/
      14. /var/lib/apt/lists/download.bloonix.de_repos_ubuntu_dists_xenial_Release:Date: Mon, 02 Jan 2017 16:35:55 +0100
      15. /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease:Date: Sun, 15 Jan 2017 18:03:42 UTC
      16. /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease:Date: Thu, 19 Jan 2017 1:14:58 UTC
      17. /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_xenial-security_InRelease:Date: Wed, 18 Jan 2017 9:09:49 UTC
      18. /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_xenial_InRelease:Date: Thu, 21 Apr 2016 23:23:46 UTC
      Display All
    • Hmm, ich sehe nicht, wo es kaputt sein soll.

      Die Doku (wiki.debian.org/RepositoryFormat) sagt:


      Date, Valid-Until

      The Date field shall specify the time at which the Release file was created. Clients updating a local on-disk cache should ignore a Release file with an earlier date than the date in the already stored Release file.

      The Valid-Until field may specify at which time the Release file should be considered expired by the client. Client behaviour on expired Release files is unspecified.

      The format of the dates is the same as for the Date field in .changes files; and as used in debian/changelog files, and documented in Policy 4.4 ( Debian changelog: debian/changelog), but all dates must be represented as an instance of UTC (Coordinated Universal Time) as it is the case e.g. in HTTP/1.1, too. Thus, generating a valid value for the Date field can be achieved by running date -R -u.

      Example:

      Date: Sat, 02 Jul 2016 05:20:50 +0000


      Ok, lass mal schauen was ein date -R -u macht:

      Source Code

      1. #> date -R -u
      2. Thu, 19 Jan 2017 19:15:50 +0000


      Und jetzt der Zeitstempel aus dem Release File des Bloonix Repos:

      Source Code

      1. #> curl -s https://download.bloonix.de/repos/ubuntu/dists/xenial/Release | grep ^Date
      2. Date: Thu, 19 Jan 2017 13:14:40 +0100


      Ich sehe keine Fehler.