On Tue, Feb 12, 2019 at 05:20:13PM +0100, Jouke Witteveen
wrote:
> I just tagged 1.20, which switches from using wpa_actiond to using wpa_cli.
> Let's keep this in [testing] for at least two weeks to see whether
> there is anything noticeable from this change.
Sounds good. Since I'm not really
Hi all,
I just tagged 1.20, which switches from using wpa_actiond to using wpa_cli.
Let's keep this in [testing] for at least two weeks to see whether
there is anything noticeable from this change.
Thanks!
- Jouke
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Network control utility based on systemd".
The branch, master has been updated
via 7cb0a5ab146f3c26bc05706bda7e3e662af5408a
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Network control utility based on systemd".
The annotated tag, 1.20 has been created
at f740dc6b4de8731345ab5b3014225b96b971707e
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official devtools repository".
The branch, master has been updated
via 62306018f2cea57aafae410f00d00d2594592e8f (commit)
On Fri, Feb 8, 2019 at 3:36 PM Emil Velikov wrote:
>
> On Thu, 7 Feb 2019 at 14:50, Jouke Witteveen via arch-projects
> wrote:
> >
> > The same functionality is provided by wpa_supplicant, so we do not need
> > an extra and Arch Linux specific dependency.
>
> T
On Thu, 7 Feb 2019 at 14:50, Jouke Witteveen via arch-projects
wrote:
>
> The same functionality is provided by wpa_supplicant, so we do not need
> an extra and Arch Linux specific dependency.
The introduction of wpa_actiond [1] hints there are issues with wpa_cli. Namely:
- partial o
On 2/7/19 8:00 PM, james harvey via arch-projects wrote:
> I guess I'm abusing devtools a bit, as a few others are. I use
> devtools to build modified official packages when necessary, and to
> build AUR packages even if they depend on other AUR packages. I add a
> local reposit
On Thu, Feb 7, 2019 at 8:14 AM Bruno Pagani wrote:
> Le 07/02/2019 à 12:14, james harvey via arch-projects a écrit :
> > I got extremely confused when I accidentally found out that the
> > MAKEFLAGS that is needed to be set for parallel building using
> > devtools is the one
On Thu, Feb 7, 2019 at 12:15 PM Eli Schwartz via arch-projects
wrote:
> On 2/7/19 6:14 AM, james harvey via arch-projects wrote:
> > I got extremely confused when I accidentally found out that the
> > MAKEFLAGS that is needed to be set for parallel building using
> > devtool
On 2/7/19 6:17 AM, james harvey via arch-projects wrote:
> It could be worth a developer diff'ing:
> * pacman::makepkg.conf and devtools::makepkg-x86_64.conf
> * pacman::pacman.conf and devtools::pacman*.conf
>
> When trying to figure out my /etc/ vs /usr/share/devt
On 2/7/19 6:14 AM, james harvey via arch-projects wrote:
> I got extremely confused when I accidentally found out that the
> MAKEFLAGS that is needed to be set for parallel building using
> devtools is the one in "/etc/makepkg.conf", instead of one like
> "/usr/share/d
The same functionality is provided by wpa_supplicant, so we do not need
an extra and Arch Linux specific dependency.
---
README | 4 ++--
contrib/PKGBUILD.in | 1 -
src/lib/auto.action | 31 ++-
src/netctl-auto | 30 +-
4
When accept_ra is set to 1, router advertisements are still ignored if
the interface is in forwarding mode. For such configurations, the
interface should have a static configuration and netctl already sets
accept_ra to 0. Setting it to 2 otherwise forces the kernel to accept
router advertisements
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Network control utility based on systemd".
The branch, master has been updated
via ea9ccfd2e249880c9b09553c3963a9b3d735faca
Hi,
Le 07/02/2019 à 12:14, james harvey via arch-projects a écrit :
> I got extremely confused when I accidentally found out that the
> MAKEFLAGS that is needed to be set for parallel building using
> devtools is the one in "/etc/makepkg.conf", instead of one like
> "
On February 7, 2019 12:17:01 PM GMT+01:00, james harvey via arch-projects
wrote:
>It could be worth a developer diff'ing:
>* pacman::makepkg.conf and devtools::makepkg-x86_64.conf
>* pacman::pacman.conf and devtools::pacman*.conf
>
>When trying to figure out my /etc/ vs /usr
It could be worth a developer diff'ing:
* pacman::makepkg.conf and devtools::makepkg-x86_64.conf
* pacman::pacman.conf and devtools::pacman*.conf
When trying to figure out my /etc/ vs /usr/share/devtools/ confusion
with MAKEFLAGS, I saw these differ in more areas than I would have
expected.
I
I got extremely confused when I accidentally found out that the
MAKEFLAGS that is needed to be set for parallel building using
devtools is the one in "/etc/makepkg.conf", instead of one like
"/usr/share/devtools/makepkg-x86_64.conf".
Turns out this is because "makechrootpkg"::20180531-4::638 is:
On Sun, Jan 27, 2019 at 3:00 AM Eli Schwartz via arch-projects
wrote:
>
> The Makefile commands in use include bash-specific features like brace
> expansion, and thus cannot run under the default /bin/sh shell as that
> may or may not be GNU bash (bash supports brace expansion e
The Makefile commands in use include bash-specific features like brace
expansion, and thus cannot run under the default /bin/sh shell as that
may or may not be GNU bash (bash supports brace expansion even in posix
mode).
Consequently, the Makefile failed to execute correctly when the system
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official devtools repository".
The branch, master has been updated
discards 450e6af53b9e429b894a4b04b03d45ddae1a9786 (commit)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official devtools repository".
The branch, master has been updated
via 450e6af53b9e429b894a4b04b03d45ddae1a9786 (commit)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official devtools repository".
The branch, master has been updated
via 8310abb3485bdf63fc3557e3020a43f9f9e03927 (commit)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official devtools repository".
The branch, master has been updated
via 7b095250030dd85684226a6191d739d2f04424a3 (commit)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official devtools repository".
The branch, master has been updated
via e9102b2ad84964cd826a63e0de605828e0528261 (commit)
On 1/18/19 10:16 AM, Morgan Adamiec via arch-projects wrote:
> On Fri, 18 Jan 2019 at 14:53, Eli Schwartz via arch-projects
> wrote:
>>
>> alpm_sync_newversion becomes alpm_sync_get_new_version and changes
>> behavior slightly. See for details:
>> https://git.archl
On Fri, 18 Jan 2019 at 14:53, Eli Schwartz via arch-projects
wrote:
>
> alpm_sync_newversion becomes alpm_sync_get_new_version and changes
> behavior slightly. See for details:
> https://git.archlinux.org/pacman.git/commit/?id=e9d91a688d1a2ebe58e8a895853debf745a529cf
> ---
&
alpm_sync_newversion becomes alpm_sync_get_new_version and changes
behavior slightly. See for details:
https://git.archlinux.org/pacman.git/commit/?id=e9d91a688d1a2ebe58e8a895853debf745a529cf
---
DO NOT MERGE THIS until after pacman 5.2 or 6 is released.
pacman does not have any good
454a9c1ec00a3ef11f3f599281127b383d
>
> This is when it was finally merged:
> https://lists.archlinux.org/pipermail/arch-projects/2018-May/004897.html
>
> It was only merged at that time, because despite my having contributed a
> patch months before which make makechrootpkg work *at a
to it happening, it's just totally not
worth my time to even try.
The last time I tried to submit a patch for devtools was here:
https://git.archlinux.org/devtools.git/commit/?id=5b3c14454a9c1ec00a3ef11f3f599281127b383d
This is when it was finally merged:
https://lists.archlinux.org/pipermail/arch-pr
hwartz wrote:
> >
> > On 1/15/19 8:56 AM, Maarten de Vries wrote:
> > > On Tue, 15 Jan 2019 at 14:41, Eli Schwartz via arch-projects
> > > wrote:
> > >>
> > >> On 1/15/19 8:34 AM, Maarten de Vries via arch-projects wrote:
> > >>
On Tue, 15 Jan 2019 at 15:03, Eli Schwartz wrote:
>
> On 1/15/19 8:56 AM, Maarten de Vries wrote:
> > On Tue, 15 Jan 2019 at 14:41, Eli Schwartz via arch-projects
> > wrote:
> >>
> >> On 1/15/19 8:34 AM, Maarten de Vries via arch-projects wrote:
> >
On 1/15/19 8:56 AM, Maarten de Vries wrote:
> On Tue, 15 Jan 2019 at 14:41, Eli Schwartz via arch-projects
> wrote:
>>
>> On 1/15/19 8:34 AM, Maarten de Vries via arch-projects wrote:
>>> These patches make it possible to build withouth a shared pacman cache
>
On Tue, 15 Jan 2019 at 14:41, Eli Schwartz via arch-projects
wrote:
>
> On 1/15/19 8:34 AM, Maarten de Vries via arch-projects wrote:
> > These patches make it possible to build withouth a shared pacman cache
> > using makechrootpkg. I need this myself because I'm
On 1/15/19 8:34 AM, Maarten de Vries via arch-projects wrote:
> These patches make it possible to build withouth a shared pacman cache
> using makechrootpkg. I need this myself because I'm building packages
> for different repositories where some of them contain packages with the
&g
Signed-off-by: Maarten de Vries
---
makechrootpkg.in | 29 +++--
1 file changed, 23 insertions(+), 6 deletions(-)
diff --git a/makechrootpkg.in b/makechrootpkg.in
index d81be84..ad65de4 100644
--- a/makechrootpkg.in
+++ b/makechrootpkg.in
@@ -38,6 +38,7 @@ usage() {
These patches make it possible to build withouth a shared pacman cache
using makechrootpkg. I need this myself because I'm building packages
for different repositories where some of them contain packages with the
same name, but different compile time configuration.
It also allows building
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The annotated tag, 20190113 has been created
at 7aa40fa976c8f51c03095619782a905e992f1157 (tag)
This needs to check the pkgbase, not the pkgname, as for split packages
we need to lookup a PKGBUILD using the basename.
Signed-off-by: Eli Schwartz
---
db-functions | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/db-functions b/db-functions
index 5c363578..65e7700f
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The annotated tag, 20190111-2 has been deleted
was 5bfe163783afeb315c64411a4649e808eda93bfa
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The annotated tag, 20190111-2 has been created
at dcb4f00944c0911c8e9f2163828a4ebc78037aea (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The branch, master has been updated
via 7a173f8298f915050778999ec8eef1322dfc0d97 (commit)
from
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The annotated tag, 20190111-2 has been created
at 5bfe163783afeb315c64411a4649e808eda93bfa (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The branch, master has been updated
via 70adbd1a69636c0524003a684c69af0f23b54539 (commit)
from
Oops, I have sent a raft of faulty tags in addition by accident that I
once git fetched from a fork. :(
Please either ignore or give me permission to backdoor your email
provider and delete the spam for you.
--
Eli Schwartz
Bug Wrangler and Trusted User
signature.asc
Description: OpenPGP
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/2017 has been created
at e3973262cca737d8c174b6292f64de6b1baeb6e6 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180502.2 has been created
at 1a3f6289ccfbb15cd8e8c3d28a8ee198fa477a30 (commit)
-
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180429.1 has been created
at ffb88bb9082b68ec928811d05c76bcab8431a37b (commit)
-
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180401 has been created
at ffedeab545c1c4f45f315adbdc7a42dea707f455 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180326 has been created
at 4075f9ed3631ac04042678ffeffa74e166d12b15 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20170610.1 has been created
at 961f0c5355e12120955d3dec08162237e5096c2b (commit)
-
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20170527.1 has been created
at 54ce226dc304ed13befb747edc329d09467b8cbd (commit)
-
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180425 has been created
at 3867f0435b2d98278657fc47558ff44c9f554247 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20170120.1 has been created
at de9f3bae65a3c488a11a998fa177921ed4cab339 (commit)
-
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20170214.1 has been created
at 92583e52b6b785b0c5c740948cb09738f3027275 (commit)
-
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20170214 has been created
at 99ff674ad4206e2e140ec4e1cc6caa7f535b8803 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20160708 has been created
at 70357110197aa7e954bd50593c36721f4d547911 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180505 has been created
at 8393137cd49de14f0f74caee8e93fa43ca881e2b (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180507.1 has been created
at a9f1927584a312900e7db29cee7daa548301ec9f (commit)
-
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20170610.3 has been created
at fcb893a28265fb9e815b88012c3f2a7d940e3888 (commit)
-
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180429 has been created
at b27f6fdadee4227ab32b8bf34fe609e5b44fdc35 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180612 has been created
at 77b61a24ab1e71f65215c968ba7b118b6ac5e10a (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180611 has been created
at 12dfdd5944ae78ff4dd6cbe0cd96a09a0d99f595 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The annotated tag, lukeshu/to-upstream/2018-03-15-archlinux+cleanup-v4 has been
created
at
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, lukeshu/to-upstream/2018-03-21-archlinux+cleanup-v9 has been created
at
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180507 has been created
at fef7b4f6e946d50fcc37a5b8a795ba1ee6a2cfc6 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The annotated tag, lukeshu/to-upstream/2018-03-16-archlinux+cleanup-v7 has been
created
at
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20180610 has been created
at 9233d18f7487c2d2b969a4b72ae9976f1dc757cd (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20170120.2 has been created
at 99ff674ad4206e2e140ec4e1cc6caa7f535b8803 (commit)
-
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, lukeshu/2011-dbscripts-repo-maintainer-merge has been created
at
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, lukeshu/to-upstream/2018-04-02-archlinux+cleanup-v10 has been created
at
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The annotated tag, lukeshu/to-upstream/2018-03-14-archlinux+cleanup-v2 has been
created
at
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The tag, parabola/20170120 has been created
at 973daf0b56132ff451913fc127521ab5fcd5d033 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The annotated tag, 20190111 has been created
at 9e45ae4063267eb123b8cae625a3afdcfde52329 (tag)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The annotated tag, lukeshu/to-upstream/2018-03-14-archlinux+cleanup-v3 has been
created
at
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The branch, master has been updated
via d5970df3a7051b7ceb5d69a345c763e9b5ed8052 (commit)
via
A semi-common pattern is for one maintainer to stage a rebuild of a
package due to e.g. cascading repository-wide python/boost/whatever
rebuilds, and then for the original maintainer of the package to not
notice and update the package in the stable repo, leaving an out of date
rebuild in staging
At the point when it was being run, the signature was not yet moved to
PKGPOOL.
Signed-off-by: Eli Schwartz
---
Discovered while debugging the verify branch.
db-update | 2 +-
test/cases/db-update.bats | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The branch, master has been updated
via 948a181f5f09ca1cc03d450081f296222ca26d2f (commit)
from
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The branch, verify-update-plus-rebuild has been created
at 77c72694e608decd63978f3ae6d941487476ef98
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Official repo DB scripts".
The branch, master has been updated
via f11a038c43270a70eafdba34ff33e134b6726a04 (commit)
via
Hi,
I am migrating a swing interop application from JavaFX-8 to JavaFX-11...
Have the ButtonBuilder, HBoxBuilder, etc. been removed? And if so, can anyone
point me to an example alternative?
Jose Heitor
On Wed, Jan 09, 2019 at 05:01:21PM -0500, Eli Schwartz via arch-projects
wrote:
> v3: string changes, consistently use BASH_SOURCE
Looks good to me. Thanks!
Florian
signature.asc
Description: PGP signature
Whenever adding new package files to the pool of distributed packages,
copy the file into a longterm archive. This is the first step to merging
the functionality of archivetools, as this implements the shared pool
while also guaranteeing that all packages are archived at the time of
entry rather
On Wed, Jan 09, 2019 at 10:45:12AM -0500, Eli Schwartz via arch-projects
wrote:
> >>>> diff --git a/db-update b/db-update
> >>>> index 313fb999..04a29bf3 100755
> >>>> --- a/db-update
> >>>> +++ b/db-u
On 1/9/19 10:34 AM, Florian Pritz wrote:
> On Wed, Jan 09, 2019 at 09:49:26AM -0500, Eli Schwartz via arch-projects
> wrote:
>>>> diff --git a/db-functions b/db-functions
>>>> index 7aeedced..b8a00b90 100644
>>>> --- a/db-functions
>
On Wed, Jan 09, 2019 at 09:49:26AM -0500, Eli Schwartz via arch-projects
wrote:
> >> diff --git a/db-functions b/db-functions
> >> index 7aeedced..b8a00b90 100644
> >> --- a/db-functions
> >> +++ b/db-functions
> >> @@ -444,4 +447,24 @@
On 1/9/19 8:00 AM, Florian Pritz wrote:
> On Tue, Jan 08, 2019 at 06:40:37PM -0500, Eli Schwartz via arch-projects
> wrote:
>> diff --git a/db-archive b/db-archive
>> new file mode 100755
>> index ..5680b9de
>> --- /dev/null
>> +++ b/db-archive
On Tue, Jan 08, 2019 at 06:40:37PM -0500, Eli Schwartz via arch-projects
wrote:
> diff --git a/db-archive b/db-archive
> new file mode 100755
> index ..5680b9de
> --- /dev/null
> +++ b/db-archive
> @@ -0,0 +1,21 @@
> +#!/bin/bash
> +
> +. "$(dirna
Prerequisite for reproducible archives of packages.
Signed-off-by: Eli Schwartz
---
test/lib/common.bash | 10 ++
1 file changed, 10 insertions(+)
diff --git a/test/lib/common.bash b/test/lib/common.bash
index bc2b4e6d..ab7d5963 100644
--- a/test/lib/common.bash
+++
Whenever adding new package files to the pool of distributed packages,
copy the file into a longterm archive. This is the first step to merging
the functionality of archivetools, as this implements the shared pool
while also guaranteeing that all packages are archived at the time of
entry rather
Overview: This training program targets students with interest in wildlife
handling, zoology, or veterinary science. Students will participate in annual
capture and release programs focused on nonhuman primates, bats, birds, and
small to medium size terrestrial mammals (rodents, marsupials,
Overview: Tamarins are notoriously difficult to track and identify in the wild,
because of their diminutive size and morphological homogeneity. In this
program, we monitor a population of ~14 tamarin groups, individually
identifiable and radio-collared, to study their space use and means of
PROGRAM OVERVIEW: Situated in the heart of the Caribbean, equidistant from
Puerto Rico and the Dominican Republic, Mona Island is often called the
Galapagos of the Caribbean. Once just a destination for pirates and privateers,
Mona is protected by the Department of Natural and Environmental
COURSE OVERVIEW
This course will take you to the Peruvian Amazon, where you will learn how
field research is conducted, assist in sample collection, and then actually
extract, amplify, sequence, and interpret genetic data to answer several
practical research questions about wildlife ecology
From: Morten Linderud
Les us source makepkg.conf settings from the environemnt. This also includes
`GNUPGHOME` which is present in `makechrootpkg`, but not included in archbuild.
Signed-off-by: Morten Linderud
---
archbuild.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wed, Dec 05, 2018 at 10:49:44AM +0100, Florian Pritz via arch-devops
wrote:
> Also thinking about this, it would be great if we could skip the pkg
> symlinks for each day's archive and only copy the db itself. All we'd
> need is to have a dedicated PackageServer= setting (like Server=, but
>
On 12/12/18 3:55 AM, Jelle van der Waa wrote:
> On 12/04/18 at 01:15pm, Eli Schwartz via arch-devops wrote:
>> On 12/4/18 1:09 PM, Eli Schwartz wrote:
>>> Whenever adding new package files to the pool of distributed packages,
>>> hardlink a copy of every package it was built with, into a
>>>
ai nostri strumenti potete individuare i profili migliori
ed al miglior prezzo con un solo click !
Consulenza ITC
La Programs & Projects Consulting e' il partner ideale per le aziende.
Proponiamo un'offerta di servizi completa ed integrata, dalla consulenza nella
progettazione di sis
501 - 600 of 1376 matches
Mail list logo