libtag packages broken on wily #8437
Comments
|
Commented by: rryan Sorry about this! Do you use flac? We only provide 1.10 because it fixes On Sun, Jan 10, 2016, 3:00 PM Mei wrote:
|
|
Commented by: daschuer We should fix this soon. Some additional Info: Among the most common FLAC issue, taglib 1.10 fixes a lot of more crashers caused by corrupt files. Mixxx links taglib directly and not like Rythmbox, Banshee, Clementine and CO via a quarantine process. |
|
Commented by: daschuer Ping! There is a forum user suffering this bug as well: |
|
Commented by: Be-ing What is the status of libtag 1.10 upstream in Ubuntu? |
|
Commented by: daschuer Still at 1.9 |
|
Commented by: markusb 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 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. |
|
Commented by: ddouthitt 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. |
|
Commented by: ddouthitt 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 The recommended upgrade was to the following( (and it failed): 2.1.1 Looking at the builds, the most recent xenial build appears to be not 6681 at all, but rather: 2.1.0 A look at apt-cache policy shows this: So it seems that I've actually had to backtrack (from git 6681 to git 6663). Hopefully the ppa has a version that works. |
|
Commented by: ddouthitt 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 The following packages have unmet dependencies: |
|
Commented by: markusb 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-src http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial main[root] # apt install mixxx The following packages have unmet dependencies: ==== Install attempt from downloaded deb package: dpkg: error processing package mixxx (--install): ==== Install attempt of libtag1-vanilla root@W530: ==== Details of libtag1 packages |
|
Commented by: markusb 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 |
|
Commented by: ddouthitt 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 The following packages have unmet dependencies: |
|
Commented by: ddouthitt Sorry about the duplicate comment.... I'd delete it but that seems impossible. |
|
Commented by: daschuer This is a really annoying issue. But only people with ppa write access can fix it. TODO: follow the libtag package renaming: We can just upload the 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 |
|
Commented by: daschuer |
|
Commented by: daschuer |
|
Commented by: daschuer If you install both packages above Clementine and Mixxx will work side by side. |
|
Commented by: markusb Thanks Daniel, your packages work ! who has access to the ppa and can update it accordingly ? Markus |
|
Commented by: rryan I think this is a sign we shouldn't be using version constraints for On Thu, Jun 28, 2018, 3:30 AM Markus wrote:
|
|
Commented by: daschuer 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. |
|
Commented by: daschuer Libtag 1.9 is really a source of issues. |
|
Commented by: markusb 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. |
|
Commented by: rafaelfrench 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. |
|
Commented by: daschuer I agree that this one should be fixed as soon as possible, but only Party stoppers at critical. |
|
Commented by: kazakore 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. |
|
Commented by: rryan 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. |
|
Commented by: rryan I went ahead and deleted taglib 1.10-0ubuntu1~xenial0 from both our beta and release PPA. |
|
Commented by: rryan 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 :). |
|
Commented by: Be-ing I completely agree with RJ on this. |
|
Commented by: kazakore 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?? |
|
Commented by: uklotzde 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. |
|
Commented by: enpy303 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 ... |
|
Commented by: Be-ing 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. |
|
Commented by: markusb 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. |
|
Issue closed with status Fix Released. |
Reported by: ddouthitt
Date: 2016-01-10T22:50:39Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp1532631
Attachments: libtag1v5-vanilla_1.11-1ubuntu2_amd64.deb, mixxx_2.1.1-0ubuntu1
2.1git6743~xenial_amd64.debI'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
/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
The text was updated successfully, but these errors were encountered: