Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Packages being worked on by the Repo Team

Discussion about the MEPIS Community's Repo.
Message
Author
User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15801
Joined: Fri Dec 15, 2006 8:07 pm

Re: Packages being worked on by the Repo Team

#971 Post by Stevo » Thu Jun 07, 2018 2:38 pm

Firefox 60.0.2 and associated langpacks.

User avatar
mmikeinsantarosa
Forum Guide
Forum Guide
Posts: 2297
Joined: Thu May 01, 2014 10:12 am

Re: Packages being worked on by the Repo Team

#972 Post by mmikeinsantarosa » Thu Jun 07, 2018 3:31 pm

Stevo wrote:
Thu Jun 07, 2018 2:38 pm
Firefox 60.0.2 and associated langpacks.
gracias
LT: MX17.1 Quad Core model: Intel Core i7-6820HQ Kernel: 4.16.0-12.1-liquorix-amd64 (64 bit)
DT: Intel(R) Core i5-3.1GHz Kernel~3.9-1-mepis64 x86_64

User avatar
oops
Forum Regular
Forum Regular
Posts: 208
Joined: Tue Apr 10, 2018 5:07 pm

Re: Packages being worked on by the Repo Team

#973 Post by oops » Thu Jun 07, 2018 4:33 pm

Stevo wrote:
Thu Jun 07, 2018 2:38 pm
Firefox 60.0.2 and associated langpacks.
Merci Stevo (et Fehlix je suppose)
$ inxi -S : System: Host:XEON Kernel: 4.16.0-xeon-01.efi x86_64 bits: 64 Desktop: Xfce 4.12.3 - Distro: MX-17.1_x64 Horizon


User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15801
Joined: Fri Dec 15, 2006 8:07 pm

Re: Packages being worked on by the Repo Team

#974 Post by Stevo » Thu Jun 07, 2018 5:07 pm

oops wrote:
Thu Jun 07, 2018 4:33 pm
Stevo wrote:
Thu Jun 07, 2018 2:38 pm
Firefox 60.0.2 and associated langpacks.
Merci Stevo (et Fehlix je suppose)
It was a relief after the multiple builds of Thunderbird.

Coming up:

Darktable 2.4.4 for MX 17 only
OBS-Studio 21.1.2

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15801
Joined: Fri Dec 15, 2006 8:07 pm

Re: Packages being worked on by the Repo Team

#975 Post by Stevo » Fri Jun 08, 2018 2:43 pm

Going to try Chromium 67.0.3396.79 using Sid's 67.0.3396.62 debian folder as a template. All the patches applied smoothly, so let's see how long it takes on the new hexacore dodecathread laptop. Used "debian/rules get-orig-source" to download, strip out files, and recompress the orig.tarball.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15801
Joined: Fri Dec 15, 2006 8:07 pm

Re: Packages being worked on by the Repo Team

#976 Post by Stevo » Fri Jun 08, 2018 3:49 pm

Well, I solved one Chromium build failure by backporting libopenjp2-7-dev, but now am stymied by a compiler error message:

Code: Select all

ui/gfx/native_pixmap_handle.cc -o obj/ui/gfx/memory_buffer_sources/native_pixmap_handle.o
../../ui/gfx/native_pixmap_handle.cc:15:49: error: 'DRM_FORMAT_MOD_INVALID' was not declared in this scope
 static_assert(NativePixmapPlane::kNoModifier == DRM_FORMAT_MOD_INVALID,
                                                 ^~~~~~~~~~~~~~~~~~~~~~
Failing that, I did get a 4.17.0 Debian-style kernel backport started building from the rc7 Debian Experimental folder template--only had to turn off some disable-ask-for-firmware patch for a USB DVB device. Let's see how many DKMS driver builds this will break. :crossfingers:

User avatar
mmikeinsantarosa
Forum Guide
Forum Guide
Posts: 2297
Joined: Thu May 01, 2014 10:12 am

Re: Packages being worked on by the Repo Team

#977 Post by mmikeinsantarosa » Fri Jun 08, 2018 6:40 pm

Stevo wrote:
Fri Jun 08, 2018 2:43 pm
Going to try Chromium 67.0.3396.79 using Sid's 67.0.3396.62 debian folder as a template. All the patches applied smoothly, so let's see how long it takes on the new hexacore dodecathread laptop. Used "debian/rules get-orig-source" to download, strip out files, and recompress the orig.tarball.
dodecathread?
...had to look that one up :p
LT: MX17.1 Quad Core model: Intel Core i7-6820HQ Kernel: 4.16.0-12.1-liquorix-amd64 (64 bit)
DT: Intel(R) Core i5-3.1GHz Kernel~3.9-1-mepis64 x86_64

User avatar
cyrilus31
Forum Regular
Forum Regular
Posts: 546
Joined: Thu Nov 03, 2016 3:24 pm

Re: Packages being worked on by the Repo Team

#978 Post by cyrilus31 » Sat Jun 09, 2018 5:58 am

mmikeinsantarosa wrote:
Fri Jun 08, 2018 6:40 pm
Stevo wrote:
Fri Jun 08, 2018 2:43 pm
Going to try Chromium 67.0.3396.79 using Sid's 67.0.3396.62 debian folder as a template. All the patches applied smoothly, so let's see how long it takes on the new hexacore dodecathread laptop. Used "debian/rules get-orig-source" to download, strip out files, and recompress the orig.tarball.
dodecathread?
...had to look that one up :p
Don't remind your Greek lesson? ;)
Thanks to AMD, Intel finally made progress

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15801
Joined: Fri Dec 15, 2006 8:07 pm

Re: Packages being worked on by the Repo Team

#979 Post by Stevo » Sat Jun 09, 2018 1:27 pm

cyrilus31 wrote:
Sat Jun 09, 2018 5:58 am
mmikeinsantarosa wrote:
Fri Jun 08, 2018 6:40 pm
Stevo wrote:
Fri Jun 08, 2018 2:43 pm
Going to try Chromium 67.0.3396.79 using Sid's 67.0.3396.62 debian folder as a template. All the patches applied smoothly, so let's see how long it takes on the new hexacore dodecathread laptop. Used "debian/rules get-orig-source" to download, strip out files, and recompress the orig.tarball.
dodecathread?
...had to look that one up :p
Don't remind your Greek lesson? ;)
Thanks to AMD, Intel finally made progress
Had to look that up first myself. I saw other webpages calling those hexacore CPUs and had to match it for the thread number. Another prefix that is supposed to be allowable is "sexacore". :p

I finally got the 4.17 kernel to build by actually looking through some READMEs in the debian folder. It turns out you're supposed to run the vanilla tarball through a script in the debian folder that massages it and removes some files--you can't just use the tarball that you downloaded. The Experimental version was also signing their amd64 and i386 kernels for Secure Boot, which caused the build to fail when I changed the versions to mx, so I had to find which files to edit to disable the signing. So I probably now know about 1% instead of 0.5% of what's going on in the build.

Booting to the 4.17 kernel eliminates the annoying boot acpi errors I was getting with earlier kernels on the bleeding-edge MSI Coffee Lake laptop, and hibernation seems to recover the desktop better. ZFS, bbswitch, Nividia 390.48, ndiswrapper, and broadcom-sta DKMS builds all complete :number1: , but Virtualbox 5.2.12 doesn't, so I'm off to see if there's a fix for that.

Edit: Actually, virtualbox-dkms 5.2.12 is fine, it was virtualbox-guest-dkms that fails...so don't try the new kernel in a Vbox guest. But it's good for the host system. :happy:

User avatar
stsoh
Forum Regular
Forum Regular
Posts: 362
Joined: Sun Aug 20, 2017 10:11 am

Re: Packages being worked on by the Repo Team

#980 Post by stsoh » Sat Jun 09, 2018 2:05 pm

remove vb-guest that has warning then reinstall vb-guest with option --force.
eg. dkms install virtualbox-guest/5.2.12 -k 4.1x.x --force

Code: Select all

$ dkms status
broadcom-sta, 6.30.223.271, 4.16.14, x86_64: installed
ndiswrapper, 1.61, 4.16.14, x86_64: installed
virtualbox, 5.2.12, 4.16.14, x86_64: installed
virtualbox-guest, 5.2.12, 4.16.14, x86_64: installed (original_module exists)
MX-17.1_x64 Horizon, G41M-P33 Combo(MS-7592), Pentium E5400 (min/max: 1203/2700 MHz), 8Gb RAM (800 MT/s),
Intel 4 Series Integrated Graphics, Realtek PCIe Fast RTL8101/2/6E, PCI Gigabit RTL8169 Ethernets.

Post Reply

Return to “CR Discussion”