Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      apt-get source ... fails

      My guess is that the base name of the source package is not the same as the one noted in the control file.

      Attachments

        Activity

          Re: apt-get source fails
          This affects the MariaDB packages.
          And the problem seems to still exist in 5.1.39-ourdelta67.

          knielsen Kristian Nielsen added a comment - Re: apt-get source fails This affects the MariaDB packages. And the problem seems to still exist in 5.1.39-ourdelta67.

          Re: apt-get source fails
          I don't know as yet whether this is a problem in the package lists that are generated by our repo software or with apt itself. At least the .tar.gz and .dsc files can be manually downloaded and extracted, so anyone can still build the packages.

          cafuego Cafuego (Inactive) added a comment - Re: apt-get source fails I don't know as yet whether this is a problem in the package lists that are generated by our repo software or with apt itself. At least the .tar.gz and .dsc files can be manually downloaded and extracted, so anyone can still build the packages.

          Re: apt-get source fails
          apt-get source mariadb-server-5.3 (eg) works now.

          knielsen Kristian Nielsen added a comment - Re: apt-get source fails apt-get source mariadb-server-5.3 (eg) works now.

          Launchpad bug id: 469401

          ratzpo Rasmus Johansson (Inactive) added a comment - Launchpad bug id: 469401

          People

            Unassigned Unassigned
            arjenlentz Arjen Lentz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.