You are not logged in.

#1 Re: Pacman / Pacman Upgrades » Luajittex broken » 2018-12-02 21:02:59

Identifying illegal opcodes is not that hard (for Andreas - honestly, I have no idea how to do it), but the tricky part is to find them in the code - just because they _are_ there doesn't mean, they'll be executed.
Similar thing happens with used libraries: we have software with references to all kinds of (outdated) libraries, which just works - probably, because the dynamic linker just loads what's available and not all versions of the required library.

#2 Re: Pacman / Pacman Upgrades » Can't update system due x265 and ffmpeg (SOLVED) » 2018-11-26 09:36:22

ah, right smile - but probably also true for x264 and other stuff providing any .so's

#3 Re: Pacman / Pacman Upgrades » Can't update system due x265 and ffmpeg (SOLVED) » 2018-11-26 09:29:08

ah, ok. It probably just means, that we need to compile ffmpeg first and x264 later, right?

#4 Re: Pacman / Pacman Upgrades » archlinux32 - Falkon will not work - lxqt » 2018-11-26 08:10:36

It looks, like all of them could be replaced by newly built ones - let's hope, the new ones are ok in all other aspects, too.

#5 Re: Pacman / Pacman Upgrades » archlinux32 - Falkon will not work - lxqt » 2018-11-26 08:02:51

sorry, I forgot about that - I'll take a look right away

#6 Re: Pacman / Pacman Upgrades » Can't update system due x265 and ffmpeg (SOLVED) » 2018-11-26 08:02:22

Andreas, thanks for fixing this. What exactly was the cycle? Maybe we should report it to upstream? (only if it will prevent us from building it "in the normal way" next time)


#7 Re: Installation » Which --- aur packages --- works with archlinux32? » 2018-11-25 08:48:05

I'd expect 95% to build just fine (with the arch=... tweak, that is) and 4.9% to require minor modifications (replace "x86_64" by "x86" or something at some places - e.g. in the source url of some binary blob) the other per-mill will just not work as is or only with major involvement.

#9 Re: Pacman / Pacman Upgrades » [Solved]cannot resolve "protobuf=", a dependency of "python-p.. » 2018-11-22 22:38:46

can you change the title of the thread to [solved], then, please?


#10 Re: Pacman / Pacman Upgrades » Broken upgrades... libidn, icu, any ETA? » 2018-11-22 22:36:08

pacman would support partial upgrades if archlinux did, but they don't.
one would need to enter all linked libraries (including their version!) as pacman dependencies.
Actually, that is something we do programatically (check "link" dependencies in our package database, but even our system is not perfect - otherwise those problems would not happen at all

#13 Re: Pacman / Pacman Upgrades » Broken upgrades... libidn, icu, any ETA? » 2018-11-22 08:23:20

rogerthat: As you figured out yourself, updating with "--ignore libidn,icu" is a bad idea - most packages use the new icu and libidn.
I recommend to update your system normally. In case, you need some of the broken packages (e.g. firefox), install abaumann's icu62 package - but keep in mind that you are then running a quite old build of a browser which does have security implications (but you are running that old browser version right now anyway).

#14 Re: Pacman / Pacman Upgrades » archlinux32 - Falkon will not work - lxqt » 2018-11-21 06:29:23

I just rescheduled those - I'll move them to stable asap when they have been built

#15 Re: Pacman / Pacman Upgrades » archlinux32 - Falkon will not work - lxqt » 2018-11-21 06:06:14

indeed - packages built against qt5*-5.11.1-*:

#16 Re: Pacman / Pacman Upgrades » Broken upgrades... libidn, icu, any ETA? » 2018-11-20 07:02:16

The title is somewhat misleading - icu is not broken, but rather too new for the mentioned packages. Honestly, I fear, we won't be building those packages there anytime soon / anytime at all - they simply come with too many/persistent problems.
Regarding libidn: We're currently experiencing trouble with our mysql database (tyzoid seems to have some server trouble - is down - and there is some internal transition in progress which makes accessing certain information in the database quite unreliable). It looks like rhythmbox was last built on 2018-08-31 (before libidn I assume), so I rescheduled it ... let's see if we get that building now.

Sry for the trouble, but we're outnumbered here.


#17 Re: Installation » eclipse-common contains 64 bits executables » 2018-11-17 12:58:52

oops, I corrected the source (upstream just put x86_64 binary sources into the arch independent "source" array) - the next built package should come with 32 bit binaries smile.
Also, I promoted you to "Reporter" on our bug tracker.


#18 Re: Announcements » icu broken » 2018-11-13 13:40:33

regarding the remaining packages:
thunderbird and firefox fail with out-of-memory repeatedly, no matter what we try (even building with makepkg outside of the usual build environment on a machine with lots of swap does not help)
gitlab and mysql-workbench have been failing to build since quite some time before this icu issue

So I don't expect them to be rebuilt anytime soon - if you really need them, use Andreas Baumann's icu62 stub package

However, should you discover a way to make the builds of any of those packages succeed, we're keen to know and implement it.


#19 Re: Announcements » icu broken » 2018-11-12 10:37:48

liborcus and libixion have now been moved to extra, too (the old versions were broken anyway)

#20 Re: Pacman / Pacman Upgrades » archlinux32 - Falkon will not work - lxqt » 2018-11-11 10:45:25

When I learn how to (programatically) extract the qt version ("0x50b01" vs. "0x20b02"), I'll add that to the database and we should be able to avoid such situations: TODO88


#21 Re: Pacman / Pacman Upgrades » archlinux32 - Chromium will not work - lxqt » 2018-11-10 18:44:31

umm, it looks, like we successfully built chromium, so another

pacman -Syu

should solve your chromium problems.

#23 Re: Pacman / Pacman Upgrades » libreoffice-fresh 6.1.1-1.0 needs to be rebuilt against icu 63.1-2.0 » 2018-11-09 07:07:29

@rascholer: I gave you permissions on the bug tracker. I'll have a look, why libreoffice is not (yet) built.

#24 Announcements » icu broken » 2018-11-08 23:41:32

Replies: 13

It seems, I managed to break several packages by updating icu. The current list (known to our database / me) is:

i686/community/0ad-a23-4.0-i686 (0ad-a23-6.0-i686 now available in [community])
i686/community/aegisub-3.2.2-28.0-i686 (aegisub-3.2.2-30.0-i686 now available in [community])
i686/community/calibre-3.31.0-1.0-i686 (calibre-3.34.0-1.0-i686 now available in [community])
i686/community/haskell-hakyll- (haskell-hakyll- now available in [community])
i686/community/kbibtex-1:0.8.1-2.1-i686 (kbibtex-1:0.8.1-3.0-i686 now available in [community])
i686/community/pandoc-citeproc- (pandoc-citeproc- now available in [community])
i686/community/scribus-1.5.4-1.0-i686 (scribus-1.5.4-5.0-i686 now available in [community])
i686/extra/chromium-69.0.3497.92-1.0-i686 (chromium-70.0.3538.77-2.0-i686 now available in [extra])
i686/extra/firefox-62.0-1-i686 (firefox-63.0.3-1.0-i686 now available in [extra])
i686/extra/libreoffice-fresh-6.1.1-1.0-i686 (libreoffice-fresh-6.1.3-1.0-i686 now available in [extra])
i686/extra/libreoffice-still-6.0.6-3.0-i686 (libreoffice-still-6.0.7-1.0-i686 now available in [extra])
i686/extra/mpd-0.20.21-1.0-i686 (mpd-0.21.1-1.0-i686 now available in [extra])
i686/extra/thunderbird-60.0-4-i686 (thunderbird-60.3.1-2.0-i686 now available in [extra])

If you require any of those packages (or packages which depend on those), please postpone updates, until we rebuilt those packages.

#25 Re: Installation » PXE boot » 2018-11-07 09:25:59

I think it's not necessary to repeat all the details from the PXE guide which andreas_baumann linked.
The only thing, I would like to know (because I never succeeded in setting that up) is, how to configure an existing isc-dhcp-server to work together with tftp and some http server - but I probably just need some more reading on the dhcp server part.


Board footer

Powered by FluxBB