Re: [Libosinfo] [osinfo-db-tools PATCH v2 08/16] Add support to meson build system

2019-07-11 Thread Fabiano Fidêncio
On Thu, Jul 11, 2019 at 9:39 PM Cole Robinson wrote: > > On 7/10/19 11:25 AM, Fabiano Fidêncio wrote: > > On Tue, Jul 9, 2019 at 12:47 PM Fabiano Fidêncio > > wrote: > > > > [snip] > > > >> +cp $BUILD_ROOT/{mingw-,}osinfo-db-tools.spec $MESON_DIST_ROOT/ > > > > I've noticed that the current stat

Re: [Libosinfo] [osinfo-db-tools PATCH v2 08/16] Add support to meson build system

2019-07-11 Thread Cole Robinson
On 7/10/19 11:25 AM, Fabiano Fidêncio wrote: > On Tue, Jul 9, 2019 at 12:47 PM Fabiano Fidêncio wrote: > > [snip] > >> +cp $BUILD_ROOT/{mingw-,}osinfo-db-tools.spec $MESON_DIST_ROOT/ > > I've noticed that the current state of osinfo-db-tools tarball is to > just include osinfo-db-tools.spec and

Re: [Libosinfo] [osinfo-db PATCH 0/2] dragonflybsd: Add eol-dates for old releases & add 5.6 info & tests

2019-07-11 Thread Cole Robinson
On 7/11/19 6:06 AM, Fabiano Fidêncio wrote: > After a conversation with DragonFly BSD folks on their IRC, I've learned that: > - a release can be considered EOL once a new once is out; > - With this in mind, let's populate the db with this missing info; > - x.y.minor releases should just be consi

Re: [Libosinfo] [osinfo-db-tools PATCH] tests: Unset OSINFO_LOCAL_DIR envvar

2019-07-11 Thread Cole Robinson
On 7/9/19 4:00 AM, Fabiano Fidêncio wrote: > Commit 1df4c0dbede tried to unset all OSINFO_*_DIR envvars but instead > of unsetting OSINFO_LOCAL_DIR it unset OSINFO_DATA_DIR, which doesn't > exist. > > Signed-off-by: Fabiano Fidêncio > --- > tests/test_osinfo_db_path.py | 4 ++-- > 1 file changed

Re: [Libosinfo] [osinfo-db PATCH 0/2] debian: Add Debian 10 info & update Debian 9 URLs

2019-07-11 Thread Cole Robinson
On 7/9/19 3:58 AM, Fabiano Fidêncio wrote: > In this series let's: > - Update the deadlinks from Debian 9 as, due to the Debian 10 release, > its ISOs have been moved to the archive; > - Add Debian 10 info; > * Unattended installation on both jeos/desktop have been tested using > Debian tre

[Libosinfo] [osinfo-db PATCH 2/2] dragonflybsd: Add 5.6 data

2019-07-11 Thread Fabiano Fidêncio
In a conversation with DragonFly BSD developers I've learned that the minor releases (x.y.minor) should not have their own entries. It's too late for fixing this for older releases, but let's follow this for new ones. Signed-off-by: Fabiano Fidêncio --- .../dragonflybsd.org/dragonflybsd-5.6.xml.

[Libosinfo] [osinfo-db PATCH 1/2] drangonflybsd: Add EOL date

2019-07-11 Thread Fabiano Fidêncio
Although DragonFlyBSD doesn't have specific EOL dates mentioned in their website, a quick chat on their development IRC channel suggested that a distro reach its EOL once a new version is released. With this in mind, we can add the EOL info based on that. Signed-off-by: Fabiano Fidêncio --- dat

[Libosinfo] [osinfo-db PATCH 0/2] dragonflybsd: Add eol-dates for old releases & add 5.6 info & tests

2019-07-11 Thread Fabiano Fidêncio
After a conversation with DragonFly BSD folks on their IRC, I've learned that: - a release can be considered EOL once a new once is out; - With this in mind, let's populate the db with this missing info; - x.y.minor releases should just be considered as x.y releases; - With this in mind, let's

[Libosinfo] [osinfo-db PATCH 2/2] install-script, rhel: Only add install-source if there's an install URL

2019-07-11 Thread Fabiano Fidêncio
When dealing with net-install ISOs, we may reach the situation where the command-line template will generate the command-line adding a "inst.repo=" but the installation URL is not present. The easiest way to deal with this is checking whether an installation URL is present and only adding "inst.re

[Libosinfo] [osinfo-db PATCH 0/2] Only add the install-source there's an install URL

2019-07-11 Thread Fabiano Fidêncio
When dealing with Fedora/CentOS net-install ISOs, we may reach the situation where the command-line template will generate the command-line adding a "inst.repo=" but the installation URL is not present. The easiest way to deal with this is checking whether an installation URL is present and only a

[Libosinfo] [osinfo-db PATCH 1/2] install-script, fedora: Only add install-source if there's an install URL

2019-07-11 Thread Fabiano Fidêncio
When dealing with net-install ISOs, we may reach the situation where the command-line template will generate the command-line adding a "inst.repo=" but the installation URL is not present. The easiest way to deal with this is checking whether an installation URL is present and only adding "inst.re