On 09/18/13 at 08:31pm, Jameson wrote:
> I upgraded to systemd 207 today, and upon reboot received several
> messages that say, "failed to open /dev/btrfs-control skipping device
> registration: No such file or directory." The btrfs problem faq
> suggests that running "mknod /dev/btrfs-control c 1
I upgraded to systemd 207 today, and upon reboot received several
messages that say, "failed to open /dev/btrfs-control skipping device
registration: No such file or directory." The btrfs problem faq
suggests that running "mknod /dev/btrfs-control c 10 234" should fix
me up. However, when I run t
I've moved pandoc back to the AUR because the latest version picked up too
many new dependencies. It was convenient to have it in [community], but
it's much saner to maintain these with the automation used by the
arch-haskell project.
I only use it for Rust's documentation generator, and don't wan
On Wed 18 Sep 2013 at 20:00, Rashif Ray Rahman wrote:
> On 18 September 2013 06:18, Xyne wrote:
> > Jonathan Steel wrote:
> >
> >>$_gitname is $srcdir/$_gitname, not $startdir/$_gitname, so it's fine. To
> >>double-check I set $SRCDEST to point somewhere else and it builds fine
> >>still.
> >
> >
On 18 September 2013 06:18, Xyne wrote:
> Jonathan Steel wrote:
>
>>$_gitname is $srcdir/$_gitname, not $startdir/$_gitname, so it's fine. To
>>double-check I set $SRCDEST to point somewhere else and it builds fine
>>still.
>
> You're right. Looking at the source of makepkg, I see now that all fun
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 6 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 14 packages missing signoffs
* 0 packages older than 14 days
