repo-manager2.8apt-default

Forum Forums General Software repo-manager2.8apt-default

  • This topic has 2 replies, 2 voices, and was last updated Dec 15-2:58 am by ile.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #95597
    Member
    ile

      Hello
      in antiX22
      repo-manager2.8, restore apt defaults fails;
      repomanager.ccp
      is it the jessie / stretch lines at 329 to 335?

          // get Debian version
          QString ver_num = getDebianVersion();
          QString ver_name;
          if (ver_num == "8") {
              ver_name = "jessie";
          } else if (ver_num == "9") {
              ver_name = "stretch";
      

      the changelog shows numerous recent update; i cannot follow after 2.6, because it lists mx-repo-manager as the source [in mx-repo-manager it is lines 353-391] so maybe i did not track the cause correctly, but it fails Restore original APT sources.

      #95674
      Member
      iznit
        Helpful
        Up
        0
        ::

        “repomanager.cpp” exists only in older versions. In newer versions ((( 0.2.6 onward ))), this code is now found in “mainwindow.cpp”…..

            // get Debian version
            QString ver_num = getDebianVersion();
            QString ver_name;
            if (ver_num == "9") {
                ver_name = "stretch";
             } else if (ver_num == "10") {
                ver_name = "buster";
            } else if (ver_num == "11") {
                ver_name = "bullseye";
            }

        …..but that portion of code seems unrelated. The routine used when restoring the default repos reads like this:

        void MainWindow::on_pb_restoreSources_clicked()
        {
            QString antix_version = shell->getCmdOut("grep -oP '(?<=DISTRIB_RELEASE=).*' /etc/lsb-release").left(2);
            if (antix_version.toInt() < 15) {
                qDebug() << "antiX version not detected or out of range: " << antix_version;
                return;
            }
            // create temp folder
            QString path = shell->getCmdOut("mktemp -d /tmp/antix-sources.XXXXXX");
            // download source files from
            QString cmd = QString("wget -q https://gitlab.com/mx-linux/MX-%1_sources/archive/master.zip -P %2").arg(antix_version).arg(path);
            if (!shell->run(cmd.toUtf8())) {
                QMessageBox::critical(this, tr("Error"),
                                      tr("Could not download original APT files."));
                return;
            }
            // extract master.zip to temp folder
            cmd = QString("unzip -q %1/master.zip -d %1/").arg(path);
            system(cmd.toUtf8());
            // move the files from the temporary directory to /etc/apt/sources.list.d/
            cmd = QString("mv -b %1/antiX-*_sources-master/* /etc/apt/sources.list.d/").arg(path);
            system(cmd.toUtf8());
            // delete temp folder
            cmd = QString("rm -rf %1").arg(path);
            system(cmd.toUtf8());
            refresh();
            QMessageBox::information(this, tr("Success"),
                                     tr("Original APT sources have been restored to the release status. User added source files in /etc/apt/sources.list.d/ have not been touched.") + "\n\n" +
                                     tr("Your new selection will take effect the next time sources are updated."));
        }

        When failure occurs, are you seeing the error message?
        ((( “Could not download original APT files.” )))

            QString cmd = QString("wget -q 
        https://gitlab.com/mx-linux/MX-%1_sources/archive/master.zip
            -P %2").arg(antix_version).arg(path);

        Nothing exists at this URL nor does the “gitlab.com/mx-linux/” namespace exist, right?

        #95684
        Member
        ile
          Helpful
          Up
          0
          ::

          yes. fail means got message Could not download original APT files.
          iznit, are you indicating that 2.8 works for you?
          did you get a fail? or restored to default status?

        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.