libtag packages broken on wily

Bug #1532631 reported by Mei
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Medium
RJ Skerry-Ryan

Bug Description

I'm running Xubuntu Wily and trying to upgrade from the system libtag 1.9 to the mixxx-provided libtag 1.10 is badly broken.

The biggest problem is that the system is looking for libtag1v5-vanilla, but the mixxx packages only provide libtag1-vanilla. This means that libtagc0 can't be installed, and fixing the apt environment means removing parole and a couple of other things entirely.

I wound up rebuilding both the system provided 1.9 and the mixxx provided 1.10 - but that didn't help beyond fixing my own dependency problems.

So now... I am running Mixxx 2.0 with libtag 1.9 - hopefully that wont cause problems.

System details:

uname -a:
Linux luna 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

lshw -short:
H/W path Device Class Description
====================================================
                             system Computer
/0 bus Motherboard
/0/0 memory 7983MiB System memory
/0/1 processor AMD Phenom(tm) 9650 Quad-Core Processor
/0/100 bridge RS880 Host Bridge
/0/100/2 bridge RS780 PCI to PCI bridge (ext gfx port 0
/0/100/2/0 display GM107 [GeForce GTX 750 Ti]
/0/100/2/0.1 multimedia NVIDIA Corporation
/0/100/a bridge RS780/RS880 PCI to PCI bridge (PCIE por
/0/100/a/0 eth0 network RTL8111/8168/8411 PCI Express Gigabit E
/0/100/11 storage SB7x0/SB8x0/SB9x0 SATA Controller [IDE
/0/100/12 bus SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
/0/100/12/1 usb3 bus OHCI PCI host controller
/0/100/12/1/2 generic BCM20702A0
/0/100/12.1 bus SB7x0 USB OHCI1 Controller
/0/100/12.1/1 usb4 bus OHCI PCI host controller
/0/100/12.1/1/2 input USB Receiver
/0/100/12.2 bus SB7x0/SB8x0/SB9x0 USB EHCI Controller
/0/100/12.2/1 usb1 bus EHCI Host Controller
/0/100/12.2/1/3 wlan0 network 802.11 n WLAN
/0/100/13 bus SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
/0/100/13/1 usb5 bus OHCI PCI host controller
/0/100/13.1 bus SB7x0 USB OHCI1 Controller
/0/100/13.1/1 usb6 bus OHCI PCI host controller
/0/100/13.2 bus SB7x0/SB8x0/SB9x0 USB EHCI Controller
/0/100/13.2/1 usb2 bus EHCI Host Controller
/0/100/14 bus SBx00 SMBus Controller
/0/100/14.1 storage SB7x0/SB8x0/SB9x0 IDE Controller
/0/100/14.2 multimedia SBx00 Azalia (Intel HDA)
/0/100/14.3 bridge SB7x0/SB8x0/SB9x0 LPC host controller
/0/100/14.4 bridge SBx00 PCI to PCI Bridge
/0/100/14.5 bus SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
/0/100/14.5/1 usb7 bus OHCI PCI host controller
/0/101 bridge Family 10h Processor HyperTransport Con
/0/102 bridge Family 10h Processor Address Map
/0/103 bridge Family 10h Processor DRAM Controller
/0/104 bridge Family 10h Processor Miscellaneous Cont
/0/105 bridge Family 10h Processor Link Control
/0/2 scsi0 storage
/0/2/0.0.0 /dev/sda disk 1TB ST31000528AS
/0/2/0.0.0/1 /dev/sda1 volume 976MiB EXT3 volume
/0/2/0.0.0/2 /dev/sda2 volume 930GiB Extended partition
/0/2/0.0.0/2/5 /dev/sda5 volume 1952MiB Linux swap / Solaris partition
/0/2/0.0.0/2/6 /dev/sda6 volume 928GiB Linux filesystem partition
/0/3 scsi3 storage
/0/3/0.0.0 /dev/cdrom disk DVDRAM GH22NS40
/0/4 scsi5 storage
/0/4/0.0.0 /dev/sdb disk 256GB TOSHIBA THNSNJ25
/0/4/0.0.0/1 /dev/sdb1 volume 976MiB EXT3 volume
/0/4/0.0.0/2 /dev/sdb2 volume 3906MiB Linux swap volume
/0/4/0.0.0/3 /dev/sdb3 volume 233GiB Extended partition
/0/4/0.0.0/3/5 /dev/sdb5 volume 233GiB Linux filesystem partition

; cat /etc/*ease
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"
NAME="Ubuntu"
VERSION="15.10 (Wily Werewolf)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 15.10"
VERSION_ID="15.10"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

; dpkg -l libtag*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
un libtag-extras0 <none> <none> (no description available)
un libtag1-rusxmm <none> <none> (no description available)
rc libtag1-vanill 1.10-0ubuntu amd64 audio meta-data library - vanilla
un libtag1c2a <none> <none> (no description available)
ii libtag1v5:amd6 1.9.1-2.4ubu amd64 audio meta-data library
ii libtag1v5-vani 1.9.1-2.4ubu amd64 audio meta-data library - vanilla
ii libtagc0:amd64 1.9.1-2.4ubu amd64 audio meta-data library - C bindi
ii libtaglib2.1-c 2.1.0.0-3 all CLI library for accessing audio a

Revision history for this message
RJ Skerry-Ryan (rryan) wrote : Re: [Bug 1532631] [NEW] libtag packages broken on wily
Download full text (6.4 KiB)

Sorry about this! Do you use flac? We only provide 1.10 because it fixes
some crashes related to decoding FLAC files.

On Sun, Jan 10, 2016, 3:00 PM Mei <email address hidden> wrote:

> Public bug reported:
>
> I'm running Xubuntu Wily and trying to upgrade from the system libtag
> 1.9 to the mixxx-provided libtag 1.10 is badly broken.
>
> The biggest problem is that the system is looking for libtag1v5-vanilla,
> but the mixxx packages only provide libtag1-vanilla. This means that
> libtagc0 can't be installed, and fixing the apt environment means
> removing parole and a couple of other things entirely.
>
> I wound up rebuilding both the system provided 1.9 and the mixxx
> provided 1.10 - but that didn't help beyond fixing my own dependency
> problems.
>
> So now... I am running Mixxx 2.0 with libtag 1.9 - hopefully that wont
> cause problems.
>
> System details:
>
> uname -a:
> Linux luna 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015
> x86_64 x86_64 x86_64 GNU/Linux
>
> lshw -short:
> H/W path Device Class Description
> ====================================================
> system Computer
> /0 bus Motherboard
> /0/0 memory 7983MiB System memory
> /0/1 processor AMD Phenom(tm) 9650 Quad-Core
> Processor
> /0/100 bridge RS880 Host Bridge
> /0/100/2 bridge RS780 PCI to PCI bridge (ext gfx
> port 0
> /0/100/2/0 display GM107 [GeForce GTX 750 Ti]
> /0/100/2/0.1 multimedia NVIDIA Corporation
> /0/100/a bridge RS780/RS880 PCI to PCI bridge
> (PCIE por
> /0/100/a/0 eth0 network RTL8111/8168/8411 PCI Express
> Gigabit E
> /0/100/11 storage SB7x0/SB8x0/SB9x0 SATA Controller
> [IDE
> /0/100/12 bus SB7x0/SB8x0/SB9x0 USB OHCI0
> Controller
> /0/100/12/1 usb3 bus OHCI PCI host controller
> /0/100/12/1/2 generic BCM20702A0
> /0/100/12.1 bus SB7x0 USB OHCI1 Controller
> /0/100/12.1/1 usb4 bus OHCI PCI host controller
> /0/100/12.1/1/2 input USB Receiver
> /0/100/12.2 bus SB7x0/SB8x0/SB9x0 USB EHCI
> Controller
> /0/100/12.2/1 usb1 bus EHCI Host Controller
> /0/100/12.2/1/3 wlan0 network 802.11 n WLAN
> /0/100/13 bus SB7x0/SB8x0/SB9x0 USB OHCI0
> Controller
> /0/100/13/1 usb5 bus OHCI PCI host controller
> /0/100/13.1 bus SB7x0 USB OHCI1 Controller
> /0/100/13.1/1 usb6 bus OHCI PCI host controller
> /0/100/13.2 bus SB7x0/SB8x0/SB9x0 USB EHCI
> Controller
> /0/100/13.2/1 usb2 bus EHCI Host Controller
> /0/100/14 bus SBx00 SMBus Controller
> /0/100/14.1 storage SB7x0/SB8x0/SB9x0 IDE Controller
> /0/100/14.2 multimedia SBx00 Azalia (Intel HDA)
> /0/100/14.3 ...

Read more...

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 2.0.1
Revision history for this message
Daniel Schürmann (daschuer) wrote :

We should fix this soon.
In the meanwhile, you can use the taglib 1.10 package provided by the Qmmp project.
https://launchpad.net/~forkotov02/+archive/ubuntu/ppa/+packages

Some additional Info:

Among the most common FLAC issue, taglib 1.10 fixes a lot of more crashers caused by corrupt files.
Some of them are listed in the change log: https://taglib.github.io/

Mixxx links taglib directly and not like Rythmbox, Banshee, Clementine and CO via a quarantine process.
This means a taglib crash crashes Mixxx, while these media players are not directly effected since they only restart their quarantine process.

Changed in mixxx:
assignee: nobody → RJ Ryan (rryan)
Revision history for this message
Daniel Schürmann (daschuer) wrote :

@rryan: can I do something to support you?

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Ping!

There is a forum user suffering this bug as well:
http://www.mixxx.org/forums/viewtopic.php?f=3&t=7905

Revision history for this message
Be (be.ing) wrote :

What is the status of libtag 1.10 upstream in Ubuntu?

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Still at 1.9

Be (be.ing)
Changed in mixxx:
milestone: 2.0.1 → none
Revision history for this message
Markus (markusb) wrote :

It looks like this problem just made it impossible to install Mixxx 2.1 in 16.04 at least. It looks like a change in the last weeks caused this. When attempting to install or upgrade I get this error:

root@W530:/etc/apt/sources.list.d# apt upgrade mixxx
...
The following packages have unmet dependencies:
 libtag1v5-vanilla : Breaks: libtag1-vanilla but 1.10-0ubuntu1~xenial0 is to be installed
E: Broken packages

For now the only way to install Mixxx is to revert to the version in the Ubuntu repositories. The downloaded apt or the ppa are not working.

Revision history for this message
Mei (ddouthitt) wrote :

I too am seeing the problem in installing 2.1.1 onto Ubuntu Xenial LTS (16.04) on amd64. I'm currently running Mixxx 2.1.0 (git 2.1 r6681) without problems.

Can we stop with the libtag issues already? Not being able to upgrade is frustrating to no end.

Revision history for this message
Mei (ddouthitt) wrote :

I got my Mixxx package for Xenial from http://downloads.mixxx.org ... the original version I had on my Ubuntu Xenial Xaurus was:

2.1.0-0ubuntu1~2.1~git6681~xenial

The recommended upgrade was to the following( (and it failed):

2.1.1~pre-ppa1~2.1~git6735~artful

Looking at the builds, the most recent xenial build appears to be not 6681 at all, but rather:

2.1.0~rc1-ppa1~2.1~git6663~xenial

A look at apt-cache policy shows this:

$ apt-cache policy mixxx
mixxx:
  Installed: 2.1.0~rc1-ppa1~2.1~git6663~xenial
  Candidate: 2.1.1-0ubuntu1~2.1~git6743~xenial
  Version table:
     2.1.1-0ubuntu1~2.1~git6743~xenial 500
        500 http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial/main amd64 Packages
 *** 2.1.0~rc1-ppa1~2.1~git6663~xenial 100
        100 /var/lib/dpkg/status
     2.0.0~dfsg-4 500
        500 http://mirror.steadfast.net/ubuntu xenial/universe amd64 Packages

So it seems that I've actually had to backtrack (from git 6681 to git 6663). Hopefully the ppa has a version that *works*.

Revision history for this message
Mei (ddouthitt) wrote :

Installing one of the betas from Mixxxbetas also fails, despite being flagged as suitable for xenial:

root@luna:/etc/apt/sources.list.d# apt-cache policy mixxx
mixxx:
  Installed: 2.1.0~rc1-ppa1~2.1~git6663~xenial
  Candidate: 2.1.2~pre~git6745-0ubuntu1~2.1~git6745~xenial
  Version table:
     2.1.2~pre~git6745-0ubuntu1~2.1~git6745~xenial 500
        500 http://ppa.launchpad.net/mixxx/mixxxbetas/ubuntu xenial/main amd64 Packages
 *** 2.1.0~rc1-ppa1~2.1~git6663~xenial 100
        100 /var/lib/dpkg/status
     2.0.0~dfsg-4 500
        500 http://mirror.steadfast.net/ubuntu xenial/universe amd64 Packages
root@luna:/etc/apt/sources.list.d# apt-get install mixxx
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mixxx : Depends: libtag1-vanilla (>= 1.10-0ubuntu1~xenial0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Revision history for this message
Markus (markusb) wrote :
Download full text (3.4 KiB)

The problem is actually not with mixxx itself, but with libtag1. Mixxx supplies a version of libtag1 as a prerequisite. But in Ubuntu there is already libtag1v5, which is a newer version. Apt is refusing to downgrade to libtag1.

So the solution must be for mixxx to either use the installed libtag1 or rename the libtag1 it needs to something else to avoid naming conflicts.

==== Install attempt from ppa:

[root] # cat /etc/apt/sources.list.d/mixxx-ubuntu-mixxx-xenial.list
deb http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial main
# deb-src http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial main

[root] # apt install mixxx
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mixxx : Depends: libtag1-vanilla (>= 1.10-0ubuntu1~xenial0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

==== Install attempt from downloaded deb package:

[root] # dpkg -i /home/markus/Downloads/mixxx_2.1.1-0ubuntu1_2.1_git6743_xenial_amd64.deb
Selecting previously unselected package mixxx.
(Reading database ... 520479 files and directories currently installed.)
Preparing to unpack .../mixxx_2.1.1-0ubuntu1_2.1_git6743_xenial_amd64.deb ...
Unpacking mixxx (2.1.1-0ubuntu1~2.1~git6743~xenial) ...
dpkg: dependency problems prevent configuration of mixxx:
 mixxx depends on libtag1-vanilla (>= 1.10-0ubuntu1~xenial0); however:
  Package libtag1-vanilla is not installed.

dpkg: error processing package mixxx (--install):
 dependency problems - leaving unconfigured
Processing triggers for menu (2.1.47ubuntu1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.2) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20180209-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Errors were encountered while processing:
 mixxx

==== Install attempt of libtag1-vanilla

root@W530:~# apt-get install libtag1-vanilla
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 libtag1v5-vanilla : Breaks: libtag1-vanilla but 1.10-0ubuntu1~xenial0 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

==== Details of libtag1 packages

[root] # apt depends libtag1v5-vanilla
libtag1v5-vanilla
  Depends: libc6 (>= 2.14)
  Depends: libgcc1 (>= 1:4.1.1)
  Depends: libstdc++6 (>= 5.2)
  Depends: zlib1g (>= 1:1.1.4)
  Conflicts: <libtag-extras0>
  Conflicts: <libtag1-rusxmms>
  Breaks: libtag1-vanilla
  Breaks: libtag1c2a (<< 1.5-5)
  Replaces: libtag1-vanilla
  Replaces: libtag1c2a (<< 1.5-5)
[root] # apt depends libtag1-vanilla...

Read more...

Revision history for this message
Markus (markusb) wrote :

After some more investigation I foud a workaround, it consists of telling the installer to ignore the dependency on libtag1-vanilla. Mixxx does install and run using the installed libtag1v5-vanilla, however I've done essentially no testing.

# dpkg --ignore-depends=libtag1-vanilla -i /home/markus/Downloads/mixxx_2.1.1-0ubuntu1_2.1_git6743_xenial_amd64.deb

Revision history for this message
Mei (ddouthitt) wrote :

Installing one of the betas from Mixxxbetas also fails, despite being flagged as suitable for xenial:

root@luna:/etc/apt/sources.list.d# apt-cache policy mixxx
mixxx:
  Installed: 2.1.0~rc1-ppa1~2.1~git6663~xenial
  Candidate: 2.1.2~pre~git6745-0ubuntu1~2.1~git6745~xenial
  Version table:
     2.1.2~pre~git6745-0ubuntu1~2.1~git6745~xenial 500
        500 http://ppa.launchpad.net/mixxx/mixxxbetas/ubuntu xenial/main amd64 Packages
 *** 2.1.0~rc1-ppa1~2.1~git6663~xenial 100
        100 /var/lib/dpkg/status
     2.0.0~dfsg-4 500
        500 http://mirror.steadfast.net/ubuntu xenial/universe amd64 Packages
root@luna:/etc/apt/sources.list.d# apt-get install mixxx
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mixxx : Depends: libtag1-vanilla (>= 1.10-0ubuntu1~xenial0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Revision history for this message
Mei (ddouthitt) wrote :

Sorry about the duplicate comment.... I'd delete it but that seems impossible.

Changed in mixxx:
milestone: none → 2.1.1
milestone: 2.1.1 → 2.1.2
Revision history for this message
Daniel Schürmann (daschuer) wrote :

This is a really annoying issue. But only people with ppa write access can fix it.

TODO: follow the libtag package renaming:
libtag1 to libtag1v5 from Xenial.

We can just upload the
libtag 1.11 package from here:
https://launchpad.net/~forkotov02/+archive/ubuntu/ppa/+packages

A workaround is to install the package 1.11 from the ppa above and hack up the deb package to require libtag1v5 instead of libtag1.

https://coderwall.com/p/hes3ha/change-the-dependencies-of-a-deb-package

Revision history for this message
Daniel Schürmann (daschuer) wrote :
Revision history for this message
Daniel Schürmann (daschuer) wrote :
Revision history for this message
Daniel Schürmann (daschuer) wrote :

If you install both packages above Clementine and Mixxx will work side by side.

Revision history for this message
Markus (markusb) wrote :

Thanks Daniel,

your packages work !

who has access to the ppa and can update it accordingly ?

Markus

Revision history for this message
RJ Skerry-Ryan (rryan) wrote : Re: [Bug 1532631] Re: libtag packages broken on wily

I think this is a sign we shouldn't be using version constraints for
anything but API compatibility -- isn't this only happening because we put
a requirement on libtag?

On Thu, Jun 28, 2018, 3:30 AM Markus <email address hidden> wrote:

> Thanks Daniel,
>
> your packages work !
>
> who has access to the ppa and can update it accordingly ?
>
> Markus
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/1532631
>
> Title:
> libtag packages broken on wily
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1532631/+subscriptions
>

Revision history for this message
Daniel Schürmann (daschuer) wrote :

This happens because our ppa provided libtag does not follow upszreams renaming, that was done, because of an incompatible programming model change.

I am still the opinion that we should provide libtag > 1.9 because it has many reported crasher.

In this case I propose to just take the qmmp taglib package source to save us from extra work.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Libtag 1.9 is really a source of issues.
https://www.mixxx.org/forums/viewtopic.php?f=3&t=1196
I am convinced that providing libtag > 1.9 is a good idea.

Revision history for this message
Markus (markusb) wrote :

Actually I think we should even go to taglib 1.11. It did fix several crashes, among others when parsing mp3 files.

Another thing: This bugs importance is labelled medium. I think this should be increased to critical.

Revision history for this message
rafaelfrench (rafaelfrench) wrote :

I agree about bug importance = critical.

During my try to install 2.1.1 I removed the 2.1.0. It was a mistake, today I do not have mixxx any more.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

I agree that this one should be fixed as soon as possible, but only Party stoppers at critical.

Revision history for this message
Dale (dj-kaza) wrote :

Surely something that prevents a software from being installed on what is likely it's most popular platform is a party stopper for many! Using the usual three point scale across Severity (how bad it is) and Impact (how many people it affects) this definitely scores a 4 out of 5, which would make it a High rather than the Medium it is currently set to at least....

I've worked places where 4 of 5 is treated the same as a full 5 of 5 as well so could be argued for Critical if you worked like that.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Oh I see -- this is caused by our fix to Bug #1532107 then, where I uploaded our taglib 1.10 package for 16.04 on 2018/5/19.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

I went ahead and deleted taglib 1.10-0ubuntu1~xenial0 from both our beta and release PPA.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

I hate to beat a dead horse :), but I think we should simply delete taglib from our PPA entirely.

As I've said dozens of times, this is not the way Linux packaging is supposed to work -- we can't customize the product experience on Linux distros because we are part of a larger ecosystem, and by doing so we just create headaches (e.g. where Clementine and Mixxx have version conflicts).

On Windows and macOS we have total control over the versioning of our dependencies, and if a crash comes along caused by one of our dependencies, it's on us to deliver the fix to users -- on Linux it's not our responsibility or our place to be forcing users to upgrade libraries. The upgrade might have unintended consequences, introducing new crashes or bugs in Mixxx or in other applications, or simply prevent them from being installed due to version conflicts.

People use old distros in part for stability, and this upgrade may be undesired from that perspective too. If users want the latest bleeding edge version of libraries they should upgrade to 18.04 or switch to a rolling release distro :).

Revision history for this message
Be (be.ing) wrote :

I completely agree with RJ on this.

Revision history for this message
Dale (dj-kaza) wrote :

I was asking some questions and then read the other thread and it all made sense. I agree the Mixxx ppa should be designed to install Mixxx with no possibility of conflict, so should be against the library versions available natively. I would say that this means we really need a Known Issues list for when we have used an updated library for specific purpose (fixes bugs.)

Also would an associated, optional ppa with just the recommended libraries, so people can try but it's easier to revert, be an idea??

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

I'm with RJ and Be. Installing Mixxx must not have any side effects!

Either link dynamically against the system library provided by the distribution (default) or compile and statically link a bundled 3rd party library (exceptional). Otherwise we need to stop support for a distribution if it doesn't meet the necessary preconditions and requirements.

One of the reasons I switched from Ubuntu to Fedora years ago was the selection of package versions contained in a distribution release in conjunction with the update policy and the PPA chaos. I never looked back.

Revision history for this message
enpy (enpy303) wrote :

I had the same problem as Markus, Daniel's updated libtag solved it. Thank you.

Btw. Maybe "compile and statically link a bundled 3rd party library (exceptional)" is a way to go here. I agree it's not really a "Linux way of doing things" but leaving bugs because of distro's old libs seems worse ...

Revision history for this message
Be (be.ing) wrote :

I think statically linking small libraries (that is, not Qt) like taglib in our PPA builds is reasonable as long as we make it a build option that is off by default so distribution packagers will still be dynamically linking.

Revision history for this message
Markus (markusb) wrote :

Actually installing Daniels updated taglib resolved it temporarily. When installing something unrelated the dependency problem came up again and I had to go back to the taglib provided by Ubuntu.

Statically linking taglib for distributions where the installed taglib is broken is probably the best option.

Changed in mixxx:
milestone: 2.1.2 → 2.1.3
status: Confirmed → Fix Released
Changed in mixxx:
milestone: 2.1.3 → 2.1.2
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8437

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.