[arch-releng] March release
Hi, I could not follow Arch development lately. Is there anything preventing me from building a new ISO tomorrow? A first test build went fien so far; just one warning about mkinitcpio's usbinput hook, but that shouldn't be an issue. Greetings, Pierre -- Pierre Schmitz, https://pierre-schmitz.com
On Thu, Feb 28, 2013 at 12:00 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
I could not follow Arch development lately. Is there anything preventing me from building a new ISO tomorrow?
Not that I'm aware of.
A first test build went fien so far; just one warning about mkinitcpio's usbinput hook, but that shouldn't be an issue.
Please use the keyboard hook instead (this should be the default now as far as I know). -t
Am 28.02.2013 12:09, schrieb Tom Gundersen:
On Thu, Feb 28, 2013 at 12:00 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
I could not follow Arch development lately. Is there anything preventing me from building a new ISO tomorrow?
Not that I'm aware of.
A first test build went fien so far; just one warning about mkinitcpio's usbinput hook, but that shouldn't be an issue.
Please use the keyboard hook instead (this should be the default now as far as I know).
What breaks if I use usbinput? This change was already committed to git. So the question is if it's worth to do a new package release for this change. -- Pierre Schmitz, https://pierre-schmitz.com
On Thu, Feb 28, 2013 at 12:14 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
What breaks if I use usbinput?
Nothing. It is an alias. Except for the warning the functionality is exactly the same.
This change was already committed to git. So the question is if it's worth to do a new package release for this change.
Not at all. Just change it for the next release to avoid the warning. -t
Am 28.02.2013 12:14, schrieb Pierre Schmitz:
Am 28.02.2013 12:09, schrieb Tom Gundersen:
On Thu, Feb 28, 2013 at 12:00 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
I could not follow Arch development lately. Is there anything preventing me from building a new ISO tomorrow?
Not that I'm aware of.
A first test build went fien so far; just one warning about mkinitcpio's usbinput hook, but that shouldn't be an issue.
Please use the keyboard hook instead (this should be the default now as far as I know).
What breaks if I use usbinput? This change was already committed to git. So the question is if it's worth to do a new package release for this change.
For the sake of correctness, why not? It takes less than a minute to do so.
On 02/28/2013 08:21 AM, Thomas Bächler wrote:
Am 28.02.2013 12:14, schrieb Pierre Schmitz:
Am 28.02.2013 12:09, schrieb Tom Gundersen:
On Thu, Feb 28, 2013 at 12:00 PM, Pierre Schmitz <pierre@archlinux.de> wrote:
I could not follow Arch development lately. Is there anything preventing me from building a new ISO tomorrow?
Not that I'm aware of.
A first test build went fien so far; just one warning about mkinitcpio's usbinput hook, but that shouldn't be an issue.
Please use the keyboard hook instead (this should be the default now as far as I know).
What breaks if I use usbinput? This change was already committed to git. So the question is if it's worth to do a new package release for this change.
For the sake of correctness, why not? It takes less than a minute to do so.
Done ;) -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
participants (4)
-
Gerardo Exequiel Pozzi
-
Pierre Schmitz
-
Thomas Bächler
-
Tom Gundersen