Mythbuntu-Repos fails to install on Linux Mint

[Grizzly]

When trying to install mythbuntu-repos with gdebi on mint10-julia-64bit: 8.8-0ubuntu0+mythbuntu~auto20101116001839 this fails with E: Sub-process /usr/bin/dpkg returned an error code (1)

In Gdebi, I see that the problem lies in Debconf (or what is handed to it): "use of unitialized value" in some Perl module (see screenshot)

In addition, in mythbuntu-control-centre, occasionally the "Repositories" tab was there twice. When it was there, it was still not possible to select a repo and an upgrade path. Now it's gone again.

Update 02/19/2013-
mythbuntu-repos.py queries lsb_release to get the distribution codename, but LinuxMint doesn't return a valid Ubuntu codename- even though the mythbuntu packages are pulled from Ubuntu upstream. The Ubuntu codename can be pulled from elsewhere, though (such as the apt db).

[Grizzly (sven-witterstein)]

I would not care, if there was a way to "wget" a signing key, to "apt-key add" the repo and then get my updates. I need to update, as the running mythtv segfaults on exiting the watching of a recording.

[Thomas Mashos (tgm4883)]

I'm not at home to check it out, but there are no perl modules in that
package. Further you can add it manually by using apt-add-repository
On Nov 21, 2010 4:15 AM, "Grizzly" <email address hidden> wrote:
> I would not care, if there was a way to "wget" a signing key, to "apt-
> key add" the repo and then get my updates. I need to update, as the
> running mythtv segfaults on exiting the watching of a recording.
>
> --
> Mythbuntu-Repos fails to install on Mint10-Julia
> https://bugs.launchpad.net/bugs/678104
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to Mythbuntu.
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New
>
> Bug description:
> When trying to install mythbuntu-repos with gdebi on mint10-julia-64bit:
8.8-0ubuntu0+mythbuntu~auto20101116001839 this fails with E: Sub-process
/usr/bin/dpkg returned an error code (1)
>
> In Gdebi, I see that the problem lies in Debconf (or what is handed to
it): "use of unitialized value" in some Perl module (see screenshot)
>
> In addition, in mythbuntu-control-centre, occasionally the "Repositories"
tab was there twice. When it was there, it was still not possible to select
a repo and an upgrade path. Now it's gone again.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mythbuntu-bugs
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
> More help : https://help.launchpad.net/ListHelp

[Thomas Mashos (tgm4883)]

The issue with this is that Linux Mint 10 doesn't report a valid Ubuntu code name when queried with lsb_release -c -s. Valid codenames would be maverick, lucid, karmic, etc. Linux Mint 10 reports "julia". Using apt-add-repository correctly adds the line as maverick, so I know it exists somewhere on the machine. I've dug pretty far into apt-add-repository and assiociated python imports, but it still looks like it pulls from lsb_release.

At this point I can't/won't fix the issue. I've put forth a question in the linuxmint irc channel regarding where that comes from, so if someone in there tells me where it comes from (needs to return 'maverick' on Linux Mint 10) or if someone here posts how I can get that then I will take another look at fixing it.

[Lucas van Staden (lvs-dedmeet)]

Hi,

Good old strace to the rescure....

strace lsb_release -c -s

open("/etc/lsb-release", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=105, ...}) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=105, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ff39b553000
read(3, "DISTRIB_ID=LinuxMint\nDISTRIB_REL"..., 8192) = 105
read(3, "", 4096) = 0
read(3, "", 8192) = 0
close(3) = 0
munmap(0x7ff39b553000, 4096) = 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ff39b553000
write(1, "lucid\n", 6lucid
) = 6

cat /etc/lsb-release

DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=9
DISTRIB_CODENAME=Isadora
DISTRIB_DESCRIPTION="Linux Mint 9 Isadora"

Changed DISTRIB_CODENAME=Isadora to DISTRIB_CODENAME=lucid

DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=9
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Linux Mint 9 Isadora"

lsb_release -c -s
lucid

mythbuntu-repo installs thereafter

[Thomas Mashos (tgm4883)]

That's great and all, but doesn't really help the issue. Linux Mint is
returning valid Ubuntu codenames from somewhere without fiddling with that.

On Sun, Dec 5, 2010 at 12:45 AM, Lucas van Staden <<email address hidden>
> wrote:

> Hi,
>
> Good old strace to the rescure....
>
> strace lsb_release -c -s
>
> open("/etc/lsb-release", O_RDONLY) = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=105, ...}) = 0
> fstat(3, {st_mode=S_IFREG|0644, st_size=105, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7ff39b553000
> read(3, "DISTRIB_ID=LinuxMint\nDISTRIB_REL"..., 8192) = 105
> read(3, "", 4096) = 0
> read(3, "", 8192) = 0
> close(3) = 0
> munmap(0x7ff39b553000, 4096) = 0
> fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7ff39b553000
> write(1, "lucid\n", 6lucid
> ) = 6
>
>
> cat /etc/lsb-release
>
> DISTRIB_ID=LinuxMint
> DISTRIB_RELEASE=9
> DISTRIB_CODENAME=Isadora
> DISTRIB_DESCRIPTION="Linux Mint 9 Isadora"
>
> Changed DISTRIB_CODENAME=Isadora to DISTRIB_CODENAME=lucid
>
> DISTRIB_ID=LinuxMint
> DISTRIB_RELEASE=9
> DISTRIB_CODENAME=lucid
> DISTRIB_DESCRIPTION="Linux Mint 9 Isadora"
>
> lsb_release -c -s
> lucid
>
> mythbuntu-repo installs thereafter
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/678104
>
> Title:
> Mythbuntu-Repos fails to install on Mint10-Julia
>

[Lucas van Staden (lvs-dedmeet)]

Just a small correction:

My strace post shows result as Lucid (correct), however, the trace was pasted incorrectly (after I had changed that value in the etc file)
The strace did return Isodara until config was changed.

I am not sure what else the issue is, but as the originator complained they cannot install mythbuntu-repos.
I had the same issue, and I really needed to go forth and install mythbuntu-repos, else my project would fail.

Making the change in the config file does return Lucid, thus the install can go on, so at least a work around until properly resolved.
Just have to remember to change the file back, else local updates may fail to mint repos.

-Lucas

[Thomas Mashos (tgm4883)]

@Lucas, I can tell you 100% that the issue is mythbuntu-repos uses lsb_release to query the codename and that linux mint doesn't return a valid Ubuntu codename when that is queried. I can't fix that until someone tells me how to get a valid ubuntu codename from Linux Mint 10 (which can be done, as I have tested here). I'll mark this as incomplete until then, that way the bug report will at least stay open for a period of time.

[Donald R. Huettl (drhuettl+launchpad)]

This patch uses the APT package info for mythbuntu-control-centre to determine the distro, rather than lsb_release.

[Albert Dente (the-albert-dente)]

This, not surprisingly, is also still an issue in LinuxMint 13 Maya, based on 12.04 (precise). I was getting an error launching mythbuntu-control-centre while it was trying to load the repositories plugin.

I applied the patch, and it worked perfectly. I actually like it better than scanning lsb-release, because it's grabbing the name right out of the apt database that we're (potentially) going to be adding repos to.

I see no way this can break any official Ubuntu releases. I recommend including the patch in the next build if possible.

[Thomas Mashos (tgm4883)]

Moving this to medium priority and targeting a 14.04 fix. After discussion, we'll attempt making a mapping table between ubuntu and mint (if one already exists, please tell me) that will populate the DB file. This should resolve it all the back to 12.04 without any additional code changes.

[Thomas Mashos (tgm4883)]

I've made a mapping file based on http://www.linuxmint.com/oldreleases.php although I wish there was a better place to grab this (so I could grab it programatically). As it stands right now, we'll need to update mint.map every new mint release. This is fixed in R321 of our weekly build script (see http://bazaar.launchpad.net/~mythbuntu/mythbuntu/mythbuntu-weekly-build/revision/321 ). We've fixed it in a way that should fix it for Mint releases petra, olivia, nadia, and maya (see http://download.mythbuntu.org/repos/repos.db ). I've pushed a new build to our build servers, so this should be fixed as soon as of right now (but you will need to push the refresh button in MCC).