Re: [arch-general] Linux 5.3 - Virtualbox 5.2.32 modules fail to build - upstream bug opened
On 09/20/2019 11:57 AM, Ralf Mardorf via arch-general wrote: > virtualbox-bin from AUR is already patched with a fix. > https://aur.archlinux.org/cgit/aur.git/commit/?h=virtualbox-bin&id=83f1870f15d86179a665dc0c6b36815a385f6fbe > > You could try to adapt it to your virtualbox-bin-5 tarball from AUR without > much editing... > > $ wget -q > https://aur.archlinux.org/cgit/aur.git/snapshot/virtualbox-bin{,-5}.tar.gz > $ tar xf virtualbox-bin.tar.gz; tar xf virtualbox-bin-5.tar.gz > $ diff -r virtualbox-bin virtualbox-bin-5 > [snip] > > ...perhaps you have good luck. Sometimes patches apply with an offset and > work out of the box. > Thank you Ralf, I have the kernel modules building with a combination of the following patches: 009-include-path.patch 015-linux-5-3.patch The 013-Makefile patch must be specific to 6.X as on 5.2.32 is throws an error: Reversed (or previously applied) patch detected! Skipping patch. Still have testing, but it looks promising. -- David C. Rankin, J.D.,P.E.
Re: [arch-general] Linux 5.3 - Virtualbox 5.2.32 modules fail to build - upstream bug opened
virtualbox-bin from AUR is already patched with a fix. https://aur.archlinux.org/cgit/aur.git/commit/?h=virtualbox-bin&id=83f1870f15d86179a665dc0c6b36815a385f6fbe You could try to adapt it to your virtualbox-bin-5 tarball from AUR without much editing... $ wget -q https://aur.archlinux.org/cgit/aur.git/snapshot/virtualbox-bin{,-5}.tar.gz $ tar xf virtualbox-bin.tar.gz; tar xf virtualbox-bin-5.tar.gz $ diff -r virtualbox-bin virtualbox-bin-5 [snip] ...perhaps you have good luck. Sometimes patches apply with an offset and work out of the box.
Re: [arch-general] Linux 5.3 - Virtualbox 5.2.32 modules fail to build - upstream bug opened
On 09/20/2019 11:13 AM, David C. Rankin wrote: > On 09/20/2019 12:48 AM, Christian Hesse wrote: >> We had to patch VirtualBox 6.0.12 as well. Probably you need something >> like this: >> https://git.archlinux.org/svntogit/community.git/tree/trunk/015-linux-5-3.patch?h=packages/virtualbox > > Thank you Christian and Ralf, I'll see if I can draw from that and make things > work. > > Also, apparently Virtualbox.org has fixes available in their test-builds page: https://www.virtualbox.org/wiki/Testbuilds The bug (mine was a duplicate of) that they are working both the 6.x and 5.x kernel issue through is: https://www.virtualbox.org/ticket/18911 -- David C. Rankin, J.D.,P.E. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Linux 5.3 - Virtualbox 5.2.32 modules fail to build - upstream bug opened
On 09/20/2019 12:48 AM, Christian Hesse wrote: > We had to patch VirtualBox 6.0.12 as well. Probably you need something > like this: > https://git.archlinux.org/svntogit/community.git/tree/trunk/015-linux-5-3.patch?h=packages/virtualbox Thank you Christian and Ralf, I'll see if I can draw from that and make things work. -- David C. Rankin, J.D.,P.E. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Recent logwatch update may need a news item?
Hi, On 20/09/19 6:51 pm, Eli Schwartz via arch-general wrote: On 9/19/19 8:29 PM, Amish via arch-general wrote: Thanks but why would one parse logs to log it back to logs? I'm not sure what this statement means, but there is no "parsing", and the only "logs" are the systemd ones. Just emailing the logs doesn't constitute re-logging it to a new log. ??? (read below) The default behaviour of earlier version of logwatch was to send email to root. (via cron) The default behavior of earlier versions of the logwatch archlinux package, yes. What about the default behavior of logwatch itself? Also, like, the vast majority of system logs aren't automatically emailed to root by the software itself. I guess the vast majority of logs in a systemd-based distro aren't emailed at all (because unlike cron, systemd does not do this by default). Umm, I am not sure if you are using logwatch? It seems that you are not. So I guess if the timer was meant to be drop in replacement for cron then it should e-mail too. Who said it was supposed to be a drop-in replacement for cron? The impression I got from looking at https://bugs.archlinux.org/task/56357 is that the timer was supposed to be a "migration from cron installs to the upstream systemd service". Only the maintainer would be able to tell what his intention was. Because current upstream .service file is more or less useless. It parses the logs (journal) and sends the output (which is logwatch report) to systemd which in turn puts the logwatch report to journal! What is the point of sending log reports (back) to journal? I will report to upstream to fix this soon, when I get time. I really don't see why you think archlinux should be opinionated and modify upstream service files. I hear your argument that the package should have a post_upgrade message. If something is buggy. That should be fixed. Ofcourse first attempt should be made to fix at upstream which I will do. But Logwatch has history of not releasing new version for long. (it took 2 and half years between 7.4.3 to 7.5.0) So if logwatch does not fix service file for long then may be maintainer can look at it. Regard, Amish.
Re: [arch-general] How to get the app folders in Gnome?
On 20.09.19 14:34, Rafael Fontenelle wrote: Hello, It works here. Please check whether you have gnome-shell 1:3.34.0+94+g3d86e6e79-1 installed. Also, notice that the created app folder might move somewhere else in the list of apps: I have 8 pages of apps and the folder went to another page to keep what seems to be alphabetic order. Cheers, Rafael I have this version installed and on two user profiles dropping one application onto another does exactly nothing. I've updated my laptop now, too. Again nothing at all when dropping application icons onto some other application icon... Am I doing it wrong??? Manuel
Re: [arch-general] Recent logwatch update may need a news item?
On 9/19/19 8:29 PM, Amish via arch-general wrote: > Thanks but why would one parse logs to log it back to logs? I'm not sure what this statement means, but there is no "parsing", and the only "logs" are the systemd ones. Just emailing the logs doesn't constitute re-logging it to a new log. > The default behaviour of earlier version of logwatch was to send email > to root. (via cron) The default behavior of earlier versions of the logwatch archlinux package, yes. What about the default behavior of logwatch itself? Also, like, the vast majority of system logs aren't automatically emailed to root by the software itself. I guess the vast majority of logs in a systemd-based distro aren't emailed at all (because unlike cron, systemd does not do this by default). > So I guess if the timer was meant to be drop in replacement for cron > then it should e-mail too. Who said it was supposed to be a drop-in replacement for cron? The impression I got from looking at https://bugs.archlinux.org/task/56357 is that the timer was supposed to be a "migration from cron installs to the upstream systemd service". I really don't see why you think archlinux should be opinionated and modify upstream service files. I hear your argument that the package should have a post_upgrade message. -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
Re: [arch-general] How to get the app folders in Gnome?
Em sex, 20 de set de 2019 às 08:09, Manuel Reimer escreveu: > > Hello, > > I've updated Gnome just now. > > 3.34 should have the new "app folders" feature by just dragging > application icons onto each other. > > This doesn't work for me. > > Is there some build error on Arch? Why is this feature missing? > > Thanks in advance > > Manuel Hello, It works here. Please check whether you have gnome-shell 1:3.34.0+94+g3d86e6e79-1 installed. Also, notice that the created app folder might move somewhere else in the list of apps: I have 8 pages of apps and the folder went to another page to keep what seems to be alphabetic order. Cheers, Rafael
[arch-general] How to get the app folders in Gnome?
Hello, I've updated Gnome just now. 3.34 should have the new "app folders" feature by just dragging application icons onto each other. This doesn't work for me. Is there some build error on Arch? Why is this feature missing? Thanks in advance Manuel