- User Since
- Jul 27 2015, 12:11 PM (177 w, 1 d)
Oct 11 2016
Fixed in Tanglu 4.0 (Dasyatis kuhlii)
Oct 9 2016
Oct 1 2016
I can not reproduce this issue anymore. The libautodie-perl library has been backported to regular chromodoris updates for a while, and the issue doesn't seem to happen with the perl-base version.
So, I think this problem is resolved.
If you can test it though, that would be awesome, to get another independent conformation.
If the bug still persists, feel free to reopen!
Thank you very much for investigating this! :-)
Jul 19 2016
Jul 16 2016
This is intentional, because adding a new arch means some overhead we don't want to add when people don't use i386, which will be the majority by now.
If you are using a 32bit app, adding i386 is a really easy task. And the new Skype client for Linux also supports amd64.
Jul 15 2016
This took ages, but I think we're done here :-)
Debian also found a solution for secure boot, which we will likely adopt for Tanglu 5.
Patch works here, please test for any issues! :-)
Jul 14 2016
This should be fixed now.
If you can, please test if this issue still exists for you!
Patch for this is on its way to out daily image builds.
Jul 1 2016
Actually, this is part of a bigger issue... The chain is:
Jun 30 2016
This was already done, but calibre still needs to migrate.
See http://qa.tanglu.org/migrations/britney_excuses.html#calibre on what is missing to make this happen :)
Jun 27 2016
Version 5.0.22-dfsg-1 is in staging, which should solve this issue.
It might need some time to migrate, apparently there are issues with that atm.
Jun 19 2016
I just tested this, the problem is gone in the latest Tanglu 4.0 (Dasyatis kuhlii) snapshot.
Looks like it worked very well! Thanks!
For the record, here is a debdiff with the changes applied in Tanglu to make dpkg work correctly in the last non-broken upload (1.18.4tanglu2).
Jun 16 2016
This should be fixed with today's nightly builds - d-i wasn't copied over to Tanglu 4.0 (Dasyatis kuhlii) corectly, so there was a kernel version mismatch.
Thanks for reporting the issue!
Jun 10 2016
I saw a gorgeous new GTK+3 Breeze theme in action at a KDE sprint this week :-)
So at least for Plasma we might have a solution (that should go into Tanglu 4.0 (Dasyatis kuhlii) soo though, when there is a release of the theme or reasonably bug-free Git snapshot can be taken).
Jun 9 2016
Jun 4 2016
May 21 2016
This fix is live on Tanglu 4.0 (Dasyatis kuhlii) already :-)
Is this still an issue?
May 19 2016
This is fixed now via a somewhat ugly patch: https://github.com/tanglu-org/calamares/commit/a76061d0646d950463ecf55356c20030221674de
Needs testing though, new live images with tis change are created when calamares >= 2.2.2-0tanglu2 migrated to the dasyatis suite.
May 16 2016
Jap, and I wonder why the package doesn't provide cron in Debian too...
The maintainer set it to provide anacron, and didn't set the package to provide cron, so I guess sd-cron isn't fully equivalent to the original cron. Anyway, it's something to find out.
Problem is that we can not insert alternatives for cron in the seed for tanglu-standard, and depending on a virtual package is not allowed...
Let's see if there is a way this can be solved...
I could reproduce this issue.
Tanglu 4.0 (Dasyatis kuhlii) might have GNOME 3.20, an updated GNOME Shell is in staging, I hope it migrates in time for the release (I will close this report as soon as it does).
May 15 2016
Okay, this issue is fixed now for d-i, please test it with the current live images (which will be generated tonight).
For Calamares, I am not yet sure how to solve this properly, it still fails the installation, likely due to packages which have not been installed (the bootloader install stage needs grub-efi to be available, which needs to be installed explicitly, and that step is probably missing).
So, Calamares needs to be investigated still, but via d-i you can install Tanglu on EFI now and have it work properly!
May 13 2016
I am thinking about solving the install-missing-locales at a global level via AppStream metadata and tools like KDE Discover and GNOME Software.
We are working on a specification for this, if it gets integrated we will not need to worry about this issue anymore.
Unfortunately, this also means that the install-missing-translations-automatically issue would also not be fixed in time for Tanglu 4.0 (Dasyatis kuhlii), because it wouldn't make sense to home-grow a solution if it will be replaced a few months later.
Mar 26 2016
Mar 20 2016
Do you think a patch to the bootloader module to install the packages would be the right way?
Yes, I think at time this is the only way this can work - I still need to look at how d-i handles this (the Debian-Installer also fails the installation with EFI due to GRUB, so I'll have to ask around how this is supposed to work).
We ship the grub-efi package on the image as a .deb package, at least.
Mar 16 2016
Is your live media up-to-date?
Usually, the live-media itself has grub-pc installed, which is not coinstallable with grub-efi.
When I run this on current Tanglu 4.0 (Dasyatis kuhlii) live media, I get:
sudo apt install grub-efi-amd64 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: efibootmgr grub-efi-amd64-bin libefivar0 The following packages will be REMOVED: grub-gfxpayload-lists grub-pc grub2 The following NEW packages will be installed: efibootmgr grub-efi-amd64 grub-efi-amd64-bin libefivar0 0 upgraded, 4 newly installed, 3 to remove and 40 not upgraded. Need to get 793 kB of archives. After this operation, 2623 kB of additional disk space will be used. Do you want to continue? [Y/n] n Abort.
Unfortunately we can't just add grub-efi-amd64-bin to the CD, because it conflicts with the other GRUB flavor, notable grub-pc, so we need to find a different solution for this.
This problem does not only affect Calamares, but also d-i, which has a .deb package available but fails to install GRUB anyway (likely due to a collision with grub-pc).
Mar 14 2016
Nice catch! Looks like /etc/issue contains the wrong version information - I'll update that soon :)
Thanks for testing!
Oh, and btw, small trick regarding Phab (to prevent ticket T`4 to be referenced so often... I also do that, maybe we will have to ask the Phab team for a way to set a different shortcut, like TT to be in line with what we use in changelogs...)
If you want to reference a Tanglu release, you can use hashtags - e.g. #dasyatis will yield Tanglu 4.0 (Dasyatis kuhlii) in the final message :)
This issue is resolved with Calamares 2.0 in Tanglu 4.0 (Dasyatis kuhlii)
Calamares 2.1 isn't on the ISO yet, but will be very soon (we obviously want the bugfixes ^^)
Fixed in Calamares 2.1
Mar 13 2016
Mar 12 2016
All issues solved - the next ISO should install properly again - unless you're on an UEFI system, then you will run into problems when grub-efi is installed, but that's a known (and different) issue.
Found problem, I think I will manage to fix this today :)
The d-i issue is fixed with the upcoming cdimage rebuild. Now on to the Calamares crash :)
Mar 11 2016
Yes, both issues are still in the works. The d-i install option should work soon (tm), can't say something about Calamares yet (other than: it shouldn't crash ^^).
Mar 7 2016
Thanks for the issue report! We are aware of the problems and are working on solving them.
The debian-installer will be easy to fix, we need to rebuild it for our current kernel.
I will investigate the Calamares crashes next, the ksmserver issue is not reproducible for me right now (all the other issues are, though).
Mar 5 2016
Looks like @Yofel resolved this one... Updates should be in dasyatis shortly :-)
Mar 3 2016
Jup, that's consistend with your initramfs being broken :-/
Smells like an environment issue, although I have no idea what could have created /usr/lib/x86_64-linux-gnu/libjson-c.so.2, unless that was done manually somehow...
Mar 2 2016
That looks right, so why does it think those are missing? (1:1.22.0-17~ or later, is required but not installed)
I'll look a bit closer at the logic determining the installed-state there.
Yeah, I am investigating that issue at time - can you maybe check which version of busybox-initramfs you have installed? Because busybox should be available by default...
The archive has a sufficiently recent version of busybox, so this error message doesn't make much sense (but we also got it on the live-image builders, which is the reason why there are no KDE live images at time).
Feb 27 2016
You mean this one? http://packages.tanglu.org/dasyatis/sni-qt
I see it...
It likely isn't in Tanglu 3.0 (Chromodoris willani) due to a RC bug at that time, we could probably reintroduce it as a backport though...
I think this issue should be resolved with the latest upload of busybox, currently in staging, will reach Tanglu 4.0 (Dasyatis kuhlii) soon.
Please check if this problem vanishes with busybox >= 1:1.22.0-18tanglu1.
Thanks for your patience!
For more information on this issue, check the corresponding Debian bug.
This issue is resolved in dpkg == 1.18.4tanglu2.
A full rebuild of all FTBFS packages in the staging area will be scheduled as soon as the new GCC has finished compiling on i386 too and is installed into the archive.
Feb 18 2016
Oh, and btw: The glibc update coming to Tanglu 4.0 (Dasyatis kuhlii) also fixes the latest security issues, as was done in Tanglu 3.0 (Chromodoris willani) before :-)
(Tanglu 3.0 (Chromodoris willani), as stable release, had priority, that's why dasyatis is a bit late (also, the delay between staging->dasyatis exists)
This is due to an issue in the glibc packaging, which has been resolved in the meantime. You can easily fix your chroot environment by creating the dropped symlink: /lib64 -> /usr/lib64 - that should fix the linker and make the system work as expected. Unfortunately, you need to do that externally, since ln won't work.