Re: [Libosinfo] [libosinfo] ubuntu18.10: Update isodata after release
Adding Didier Roche to the loop. On Thu, Nov 15, 2018 at 3:36 PM Fabiano Fidêncio wrote: > > Signed-off-by: Fabiano Fidêncio > --- > .../ubuntu18.10/cosmic-desktop-amd64.iso.txt | 4 +-- > .../cosmic-live-server-amd64.iso.txt | 29 +++ > .../ubuntu18.10/cosmic-server-amd64.iso.txt | 6 ++-- > .../ubuntu18.10/cosmic-server-arm64.iso.txt | 6 ++-- > .../ubuntu18.10/cosmic-server-ppc64el.iso.txt | 2 +- > .../ubuntu18.10/cosmic-server-s390x.iso.txt | 8 ++--- > 6 files changed, 42 insertions(+), 13 deletions(-) > create mode 100644 > tests/isodata/ubuntu/ubuntu18.10/cosmic-live-server-amd64.iso.txt > > diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-desktop-amd64.iso.txt > b/tests/isodata/ubuntu/ubuntu18.10/cosmic-desktop-amd64.iso.txt > index 9f35b22..ad94849 100644 > --- a/tests/isodata/ubuntu/ubuntu18.10/cosmic-desktop-amd64.iso.txt > +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-desktop-amd64.iso.txt > @@ -11,7 +11,7 @@ Bibliographic File id: > Volume set size is: 1 > Volume set sequence number is: 1 > Logical block size is: 2048 > -Volume size is: 978240 > +Volume size is: 976320 > El Torito VD version 1 found, boot catalog is in sector 194 > Joliet with UCS level 3 found > Rock Ridge signatures version 1 found > @@ -26,4 +26,4 @@ Eltorito validation header: > Load segment 0 > Sys type 0 > Nsect 4 > -Bootoff E99EC 956908 > +Bootoff E9066 954470 > diff --git > a/tests/isodata/ubuntu/ubuntu18.10/cosmic-live-server-amd64.iso.txt > b/tests/isodata/ubuntu/ubuntu18.10/cosmic-live-server-amd64.iso.txt > new file mode 100644 > index 000..7e25c68 > --- /dev/null > +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-live-server-amd64.iso.txt > @@ -0,0 +1,29 @@ > +CD-ROM is in ISO 9660 format > +System id: > +Volume id: Ubuntu-Server 18.10 amd64 > +Volume set id: > +Publisher id: > +Data preparer id: XORRISO-1.2.4 2012.07.20.130001, LIBISOBURN-1.2.4, > LIBISOFS-1.2.4, LIBBURN-1.2.4 > +Application id: > +Copyright File id: > +Abstract File id: > +Bibliographic File id: > +Volume set size is: 1 > +Volume set sequence number is: 1 > +Logical block size is: 2048 > +Volume size is: 451072 > +El Torito VD version 1 found, boot catalog is in sector 196 > +Joliet with UCS level 3 found > +Rock Ridge signatures version 1 found > +Eltorito validation header: > +Hid 1 > +Arch 0 (x86) > +ID '' > +Key 55 AA > +Eltorito defaultboot header: > +Bootid 88 (bootable) > +Boot media 0 (No Emulation Boot) > +Load segment 0 > +Sys type 0 > +Nsect 4 > +Bootoff 68EDF 429791 > diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-amd64.iso.txt > b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-amd64.iso.txt > index 2d45260..3574006 100644 > --- a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-amd64.iso.txt > +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-amd64.iso.txt > @@ -11,8 +11,8 @@ Bibliographic File id: > Volume set size is: 1 > Volume set sequence number is: 1 > Logical block size is: 2048 > -Volume size is: 370688 > -El Torito VD version 1 found, boot catalog is in sector 2125 > +Volume size is: 367104 > +El Torito VD version 1 found, boot catalog is in sector 2115 > Joliet with UCS level 3 found > Rock Ridge signatures version 1 found > Eltorito validation header: > @@ -26,4 +26,4 @@ Eltorito validation header: > Load segment 0 > Sys type 0 > Nsect 4 > -Bootoff DEA5 56997 > +Bootoff DD43 56643 > diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-arm64.iso.txt > b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-arm64.iso.txt > index 0575849..7729543 100644 > --- a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-arm64.iso.txt > +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-arm64.iso.txt > @@ -11,8 +11,8 @@ Bibliographic File id: > Volume set size is: 1 > Volume set sequence number is: 1 > Logical block size is: 2048 > -Volume size is: 370519 > -El Torito VD version 1 found, boot catalog is in sector 4082 > +Volume size is: 368334 > +El Torito VD version 1 found, boot catalog is in sector 4058 > Joliet with UCS level 3 found > Rock Ridge signatures version 1 found > Eltorito validation header: > @@ -26,4 +26,4 @@ Eltorito validation header: > Load segment 0 > Sys type 0 > Nsect 3C0 > -Bootoff 1A17E 106878 > +Bootoff 1A245 107077 > diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-ppc64el.iso.txt > b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-ppc64el.iso.txt > index 51e26d1..081c295 100644 > --- a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-ppc64el.iso.txt > +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-ppc64el.iso.txt > @@ -11,7 +11,7 @@ Bibliographic File id: > Volume set size is: 1 > Volume set sequence number is: 1 > Logical block size is: 2048 > -Volume size is: 398772 > +Volume size is: 396150 > CD-ROM uses ISO
Re: [Libosinfo] [osinfo-db PATCH] ubuntu18.10: Update data after release
Adding Didier Roche to the loop On Thu, Nov 15, 2018 at 3:36 PM Fabiano Fidêncio wrote: > > Signed-off-by: Fabiano Fidêncio > --- > data/os/ubuntu.com/ubuntu-18.10.xml.in | 21 +++-- > 1 file changed, 15 insertions(+), 6 deletions(-) > > diff --git a/data/os/ubuntu.com/ubuntu-18.10.xml.in > b/data/os/ubuntu.com/ubuntu-18.10.xml.in > index 73e0b52..64aef8e 100644 > --- a/data/os/ubuntu.com/ubuntu-18.10.xml.in > +++ b/data/os/ubuntu.com/ubuntu-18.10.xml.in > @@ -14,7 +14,6 @@ > http://ubuntu.com/ubuntu/18.04"/> > http://ubuntu.com/ubuntu/18.04"/> > > -prerelease > 2018-10-18 > 2019-01-31 > > @@ -33,15 +32,25 @@ > > > > - > http://cdimage.ubuntu.com/ubuntu-server/daily/current/cosmic-server-amd64.iso > + > http://cdimage.ubuntu.com/ubuntu/releases/18.10/release/ubuntu-18.10-server-amd64.iso > > Ubuntu-Server 18.10(.\d)? amd64 > +751828992 > >install/vmlinuz >install/initrd.gz > > > - > http://cdimage.ubuntu.com/daily-live/current/cosmic-desktop-amd64.iso > + > http://releases.ubuntu.com/18.10/ubuntu-18.10-live-server-amd64.iso > + > +Ubuntu-Server 18.10(.\d)? amd64 > +923795456 > + > + install/vmlinuz > + install/initrd.gz > + > + > + > http://releases.ubuntu.com/18.10/ubuntu-18.10-desktop-amd64.iso > > Ubuntu 18.10(.\d)? amd64 > > @@ -49,19 +58,19 @@ >casper/initrd.lz > > > - > http://cdimage.ubuntu.com/ubuntu-server/daily/current/cosmic-server-arm64.iso > + > http://cdimage.ubuntu.com/ubuntu/releases/18.10/release/ubuntu-18.10-server-arm64.iso > > Ubuntu-Server 18.10(.\d)? arm64 > > > > - > http://cdimage.ubuntu.com/ubuntu-server/daily/current/cosmic-server-ppc64el.iso > + > http://cdimage.ubuntu.com/ubuntu/releases/18.10/release/ubuntu-18.10-server-ppc64el.iso > > Ubuntu-Server 18.10(.\d)? ppc64 > > > > - > http://cdimage.ubuntu.com/ubuntu-server/daily/current/cosmic-server-s390x.iso > + > http://cdimage.ubuntu.com/ubuntu/releases/18.10/release/ubuntu-18.10-server-s390x.iso > > Ubuntu-Server 18.10(.\d)? s390x > > -- > 2.19.1 > ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [osinfo-db PATCH 2/2] caasp: Add caasp-unknown info
>>> On 11/15/2018 at 03:03 PM, Fabiano Fidêncio wrote: > In a similar way of what's done on openSUSE and Fedora, let's have an > "unknown" entry for CaaSP that would cover any possible future release > while the proper release is not added to our db. > > Signed-off-by: Fabiano Fidêncio > --- > data/os/suse.com/caasp-unknown.xml.in | 37 +++ > 1 file changed, 37 insertions(+) > create mode 100644 data/os/suse.com/caasp-unknown.xml.in > > diff --git a/data/os/suse.com/caasp-unknown.xml.in > b/data/os/suse.com/caasp-unknown.xml.in > new file mode 100644 > index 000..363c55a > --- /dev/null > +++ b/data/os/suse.com/caasp-unknown.xml.in > @@ -0,0 +1,37 @@ > + > + > + http://suse.com/caasp/unknown;> > +caasp-unknown > +<_name>SUSE CaaS Platform Unknown > +unknown > +<_vendor>SUSE > +SUSE > +linux > +caasp > +http://suse.com/caasp/3.0"/> > +http://suse.com/caasp/3.0"/> > + > + > + > +LINUX > + > SUSE-CaaS-Platform-([4-9]|[1-9][0-9]).0-DVD-x86_64.* > + > + boot/x86_64/loader/linux > + boot/x86_64/loader/initrd > + > + > + > + > +5 > +2147483648 > +21474836480 > + > + > +24 > +8589934592 > +42949672960 > + > + > + > + > -- > 2.19.1 This one also looks good. Thanks, - Charles ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [PATCH 1/2] Revert "caasp: Adjust caasp[1-3].0 volume-id regex"
This reverts commit 50b5dad70b5c6eebd5c365a340291ee76630d2c2, which was wrong and broke test-isodata. This is totally my bad that didn't run `make check` before actually submitting the patches. Signed-off-by: Fabiano Fidêncio --- Already pushed as trivial/build fix. --- data/os/suse.com/caasp-1.0.xml.in | 2 +- data/os/suse.com/caasp-2.0.xml.in | 2 +- data/os/suse.com/caasp-3.0.xml.in | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/data/os/suse.com/caasp-1.0.xml.in b/data/os/suse.com/caasp-1.0.xml.in index 2286ed4..ba0bcab 100644 --- a/data/os/suse.com/caasp-1.0.xml.in +++ b/data/os/suse.com/caasp-1.0.xml.in @@ -17,7 +17,7 @@ LINUX -SUSE-CaaS-Platform-1.0-DVD-x86_64.* +SUSE-CaaS-Platform-1.0-DVD-x86_6 boot/x86_64/loader/linux boot/x86_64/loader/initrd diff --git a/data/os/suse.com/caasp-2.0.xml.in b/data/os/suse.com/caasp-2.0.xml.in index 17a76fc..0463564 100644 --- a/data/os/suse.com/caasp-2.0.xml.in +++ b/data/os/suse.com/caasp-2.0.xml.in @@ -18,7 +18,7 @@ LINUX -SUSE-CaaS-Platform-2.0-DVD-x86_64.* +SUSE-CaaS-Platform-2.0-DVD-x86_6 boot/x86_64/loader/linux boot/x86_64/loader/initrd diff --git a/data/os/suse.com/caasp-3.0.xml.in b/data/os/suse.com/caasp-3.0.xml.in index 44290a3..2c04394 100644 --- a/data/os/suse.com/caasp-3.0.xml.in +++ b/data/os/suse.com/caasp-3.0.xml.in @@ -17,7 +17,7 @@ LINUX -SUSE-CaaS-Platform-3.0-DVD-x86_64.* +SUSE-CaaS-Platform-3.0-DVD-x86_6 boot/x86_64/loader/linux boot/x86_64/loader/initrd -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [PATCH 2/2] caasp: Add caasp-unknown info
In a similar way of what's done on openSUSE and Fedora, let's have an "unknown" entry for CaaSP that would cover any possible future release while the proper release is not added to our db. Signed-off-by: Fabiano Fidêncio --- Already pushed as trivial/build fix. --- data/os/suse.com/caasp-unknown.xml.in | 37 +++ 1 file changed, 37 insertions(+) create mode 100644 data/os/suse.com/caasp-unknown.xml.in diff --git a/data/os/suse.com/caasp-unknown.xml.in b/data/os/suse.com/caasp-unknown.xml.in new file mode 100644 index 000..363c55a --- /dev/null +++ b/data/os/suse.com/caasp-unknown.xml.in @@ -0,0 +1,37 @@ + + + http://suse.com/caasp/unknown;> +caasp-unknown +<_name>SUSE CaaS Platform Unknown +unknown +<_vendor>SUSE +SUSE +linux +caasp +http://suse.com/caasp/3.0"/> +http://suse.com/caasp/3.0"/> + + + +LINUX + SUSE-CaaS-Platform-([4-9]|[1-9][0-9]).0-DVD-x86_64.* + + boot/x86_64/loader/linux + boot/x86_64/loader/initrd + + + + +5 +2147483648 +21474836480 + + +24 +8589934592 +42949672960 + + + + -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [osinfo-db PATCH v2 3/4] rhel: Add RHEL-8 unknown info
In a similar way of what's done on openSUSE and Fedora, let's have an "unknown" entry for RHEL-8 that would cover any possible future release while the proper release is not added to our db. Signed-off-by: Fabiano Fidêncio --- data/os/redhat.com/rhel-8-unknown.xml.in | 75 1 file changed, 75 insertions(+) create mode 100644 data/os/redhat.com/rhel-8-unknown.xml.in diff --git a/data/os/redhat.com/rhel-8-unknown.xml.in b/data/os/redhat.com/rhel-8-unknown.xml.in new file mode 100644 index 000..d62071a --- /dev/null +++ b/data/os/redhat.com/rhel-8-unknown.xml.in @@ -0,0 +1,75 @@ + + + http://redhat.com/rhel/8-unknown;> +rhel8-unknown +<_name>Red Hat Enterprise Linux 8 Unknown +8-unknown +<_vendor>Red Hat, Inc +linux +rhel +Maipo +http://redhat.com/rhel/8.0"/> +http://redhat.com/rhel/8.0"/> + + + +LINUX +.*RHEL-8-([1-9]|[1-9][0-9]).*x86_64.* + + isolinux/vmlinuz + isolinux/initrd.img + + + + + LINUX + RHEL-8-([1-9]|[1-9][0-9]).*aarch64$ + + + + + + PPC + RHEL[-_]8.([1-9]|[1-9][0-9]).*ppc64le$ + + + + + + LINUX + RHEL-8-([1-9]|[1-9][0-9]).*s390x$ + + + + + +1 +10 +2147483648 +10737418240 + + + +4 +2147483648 +21474836480 + + + + + +1 +10 +1073741824 +10737418240 + + + +10 +1073741824 +10737418240 + + + + -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [osinfo-db PATCH v2 4/4] rhel: Add RHEL unknown info
From: Fabiano Fidêncio In a similar way of what's done on openSUSE and Fedora, let's have an "unknown" entry for RHEL that would cover any possible future releases while the proper release is not added to our db. Signed-off-by: Fabiano Fidêncio --- data/os/redhat.com/rhel-unknown.xml.in | 80 ++ 1 file changed, 80 insertions(+) create mode 100644 data/os/redhat.com/rhel-unknown.xml.in diff --git a/data/os/redhat.com/rhel-unknown.xml.in b/data/os/redhat.com/rhel-unknown.xml.in new file mode 100644 index 000..180c666 --- /dev/null +++ b/data/os/redhat.com/rhel-unknown.xml.in @@ -0,0 +1,80 @@ + + + http://redhat.com/rhel/unknown;> +rhel-unknown +<_name>Red Hat Enterprise Linux Unknown +unknown +<_vendor>Red Hat, Inc +linux +rhel +http://redhat.com/rhel/8-unknown"/> + + + +LINUX +RHEL-(9|[1-9][0-9])-([0-9]|[1-9][0-9]).*x86_64$ + + isolinux/vmlinuz + isolinux/initrd.img + + + + + LINUX + RHEL-(9|[1-9][0-9])-([0-9]|[1-9][0-9]).*aarch64$ + + + + + + PPC + RHEL-(9|[1-9][0-9])-([0-9]|[1-9][0-9]).*ppc64$ + + + + + + PPC + RHEL[_-](9|[1-9][0-9])[_-]([0-9]|[1-9][0-9]).*ppc64le$ + + + + + + LINUX + RHEL-(9|[1-9][0-9])-([0-9]|[1-9][0-9]).*s390x$ + + + + + +1 +10 +2147483648 +10737418240 + + + +40 +2147483648 +21474836480 + + + + + +1 +10 +1073741824 +10737418240 + + + +10 +1073741824 +10737418240 + + + + -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [osinfo-db PATCH 0/6] Add "unknown" entries for Enterprise distros
>>> On 11/15/2018 at 02:26 AM, Fabiano Fidêncio wrote: > On Mon, 2018-11-05 at 10:05 +0100, Fabiano Fidêncio wrote: >> Although new releases are always patched downstream to support >> themselves, upstream is always behind as the new (or in development) >> releases will only be part of osinfo-db after they are released. >> >> One way to solve this issue is adding support to "unknown" entries, >> in >> the same way we have for Fedora and openSUSE, and make the new (or in >> development) release be at least recoginzed and have the proper >> devices >> loaded for those who are using them in any distro. > > Charles, may I get your input in the SUSE's related part of this > series? Shall I also add an entry for CaaS Platform as well? Yes. They do have public betas so this would be useful for pre-release detection. Thanks, - Charles ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [osinfo-db PATCH 1/2] caasp: Adjust caasp[1-3].0 volume-id regex
Signed-off-by: Fabiano Fidêncio --- data/os/suse.com/caasp-1.0.xml.in | 2 +- data/os/suse.com/caasp-2.0.xml.in | 2 +- data/os/suse.com/caasp-3.0.xml.in | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/data/os/suse.com/caasp-1.0.xml.in b/data/os/suse.com/caasp-1.0.xml.in index ba0bcab..2286ed4 100644 --- a/data/os/suse.com/caasp-1.0.xml.in +++ b/data/os/suse.com/caasp-1.0.xml.in @@ -17,7 +17,7 @@ LINUX -SUSE-CaaS-Platform-1.0-DVD-x86_6 +SUSE-CaaS-Platform-1.0-DVD-x86_64.* boot/x86_64/loader/linux boot/x86_64/loader/initrd diff --git a/data/os/suse.com/caasp-2.0.xml.in b/data/os/suse.com/caasp-2.0.xml.in index 0463564..17a76fc 100644 --- a/data/os/suse.com/caasp-2.0.xml.in +++ b/data/os/suse.com/caasp-2.0.xml.in @@ -18,7 +18,7 @@ LINUX -SUSE-CaaS-Platform-2.0-DVD-x86_6 +SUSE-CaaS-Platform-2.0-DVD-x86_64.* boot/x86_64/loader/linux boot/x86_64/loader/initrd diff --git a/data/os/suse.com/caasp-3.0.xml.in b/data/os/suse.com/caasp-3.0.xml.in index 2c04394..44290a3 100644 --- a/data/os/suse.com/caasp-3.0.xml.in +++ b/data/os/suse.com/caasp-3.0.xml.in @@ -17,7 +17,7 @@ LINUX -SUSE-CaaS-Platform-3.0-DVD-x86_6 +SUSE-CaaS-Platform-3.0-DVD-x86_64.* boot/x86_64/loader/linux boot/x86_64/loader/initrd -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [osinfo-db PATCH 2/2] caasp: Add caasp-unknown info
In a similar way of what's done on openSUSE and Fedora, let's have an "unknown" entry for CaaSP that would cover any possible future release while the proper release is not added to our db. Signed-off-by: Fabiano Fidêncio --- data/os/suse.com/caasp-unknown.xml.in | 37 +++ 1 file changed, 37 insertions(+) create mode 100644 data/os/suse.com/caasp-unknown.xml.in diff --git a/data/os/suse.com/caasp-unknown.xml.in b/data/os/suse.com/caasp-unknown.xml.in new file mode 100644 index 000..363c55a --- /dev/null +++ b/data/os/suse.com/caasp-unknown.xml.in @@ -0,0 +1,37 @@ + + + http://suse.com/caasp/unknown;> +caasp-unknown +<_name>SUSE CaaS Platform Unknown +unknown +<_vendor>SUSE +SUSE +linux +caasp +http://suse.com/caasp/3.0"/> +http://suse.com/caasp/3.0"/> + + + +LINUX + SUSE-CaaS-Platform-([4-9]|[1-9][0-9]).0-DVD-x86_64.* + + boot/x86_64/loader/linux + boot/x86_64/loader/initrd + + + + +5 +2147483648 +21474836480 + + +24 +8589934592 +42949672960 + + + + -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [osinfo-db PATCH v2 0/4] Add "unknown" entries for Enterprise distros
Although new releases are always patched downstream to support themselves, upstream is always behind as the new (or in development) releases will only be part of osinfo-db after they are released. One way to solve this issue is adding support to "unknown" entries, in the same way we have for Fedora and openSUSE, and make the new (or in development) release be at least recoginzed and have the proper devices loaded for those who are using them in any distro. This patch series depends on: https://www.redhat.com/archives/libosinfo/2018-November/msg00152.html - Changes since v1: https://www.redhat.com/archives/libosinfo/2018-November/msg00030.html - SUSE part has been already reviewed and pushed. - Added RHEL-8 unknown as RHEL-8 Beta has been announced Today Fabiano Fidêncio (4): rhel: Add RHEL-6 unknown info rhel: Add RHEL-7 unknown info rhel: Add RHEL-8 unknown info rhel: Add RHEL unknown info data/os/redhat.com/rhel-6-unknown.xml.in | 68 ++ data/os/redhat.com/rhel-7-unknown.xml.in | 87 data/os/redhat.com/rhel-8-unknown.xml.in | 75 data/os/redhat.com/rhel-unknown.xml.in | 80 ++ 4 files changed, 310 insertions(+) create mode 100644 data/os/redhat.com/rhel-6-unknown.xml.in create mode 100644 data/os/redhat.com/rhel-7-unknown.xml.in create mode 100644 data/os/redhat.com/rhel-8-unknown.xml.in create mode 100644 data/os/redhat.com/rhel-unknown.xml.in -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [osinfo-db PATCH v2 2/4] rhel: Add RHEL-7 unknown info
From: Fabiano Fidêncio In a similar way of what's done on openSUSE and Fedora, let's have an "unknown" entry for RHEL-7 that would cover any possible future release while the proper release is not added to our db. Signed-off-by: Fabiano Fidêncio --- data/os/redhat.com/rhel-7-unknown.xml.in | 87 1 file changed, 87 insertions(+) create mode 100644 data/os/redhat.com/rhel-7-unknown.xml.in diff --git a/data/os/redhat.com/rhel-7-unknown.xml.in b/data/os/redhat.com/rhel-7-unknown.xml.in new file mode 100644 index 000..94dd932 --- /dev/null +++ b/data/os/redhat.com/rhel-7-unknown.xml.in @@ -0,0 +1,87 @@ + + + http://redhat.com/rhel/7-unknown;> +rhel7-unknown +<_name>Red Hat Enterprise Linux 7 Unknown +7-unknown +<_vendor>Red Hat, Inc +linux +rhel +Maipo +http://redhat.com/rhel/7.6"/> +http://redhat.com/rhel/7.6"/> + + + +LINUX +.*RHEL-7.([7-9]|[1-9][0-9]).*x86_64.* + + isolinux/vmlinuz + isolinux/initrd.img + + + + + LINUX + RHEL-7.([7-9]|[1-9][0-9]).*aarch64$ + + + + + + PPC + RHEL[-_]7.([7-9]|[1-9][0-9]).*ppc64$ + + + + + + PPC + RHEL[-_]7.([7-9]|[1-9][0-9]).*ppc64le$ + + + + + + LINUX + RHEL-7.([7-9]|[1-9][0-9]).*s390x$ + + + + + +1 +10 +2147483648 +10737418240 + + + +4 +2147483648 +21474836480 + + + + + +1 +10 +1073741824 +10737418240 + + + +10 +1073741824 +10737418240 + + + + + + + + + -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [osinfo-db PATCH v2 1/4] rhel: Add RHEL-6 unknown info
From: Fabiano Fidêncio In a similar way of what's done on openSUSE and Fedora, let's have an "unknown" entry for RHEL-6 that would cover any possible future release while the proper release is not added to our db. Signed-off-by: Fabiano Fidêncio --- data/os/redhat.com/rhel-6-unknown.xml.in | 68 1 file changed, 68 insertions(+) create mode 100644 data/os/redhat.com/rhel-6-unknown.xml.in diff --git a/data/os/redhat.com/rhel-6-unknown.xml.in b/data/os/redhat.com/rhel-6-unknown.xml.in new file mode 100644 index 000..4d2c6a3 --- /dev/null +++ b/data/os/redhat.com/rhel-6-unknown.xml.in @@ -0,0 +1,68 @@ + + + http://redhat.com/rhel/6-unknown;> +rhel6-unknown +<_name>Red Hat Enterprise Linux 6 Unknown +6-unknown +<_vendor>Red Hat, Inc +linux +rhel +Santiago +http://redhat.com/rhel/6.10"/> +http://redhat.com/rhel/6.10"/> + +2024-06-30 + + + +LINUX +RHEL-6.(1[1-9]|[2-9][0-9]) .*.i386$ + + isolinux/vmlinuz + isolinux/initrd.img + + + +LINUX +RHEL-6.(1[1-9]|[2-9][0-9]) .*.x86_64$ + + isolinux/vmlinuz + isolinux/initrd.img + + + +PPC +RHEL-6.(1[1-9]|[2-9][0-9]) .*.ppc64$ + + isolinux/vmlinuz + isolinux/initrd.img + + + +LINUX +RHEL-6.(1[1-9]|[2-9][0-9]) .*.s390x$ + + isolinux/vmlinuz + isolinux/initrd.img + + + + +1 +536870912 + + + +4 +1073741824 +9663676416 + + + + + + + + + -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [osinfo-db PATCH 5/6] suse: Add SLE-15-unknown info
Charles, On Thu, Nov 15, 2018 at 7:48 PM Charles Arnold wrote: > > >>> On 11/5/2018 at 02:05 AM, Fabiano Fidêncio wrote: > > In a similar way of what's done on openSUSE and Fedora, let's have an > > "unknown" entry for SLE-15 that would cover any possible future release > > while the proper release is not added to our db. > > > > Signed-off-by: Fabiano Fidêncio > > --- > > data/os/suse.com/sle-15-unknown.xml.in | 63 ++ > > 1 file changed, 63 insertions(+) > > create mode 100644 data/os/suse.com/sle-15-unknown.xml.in > > > > diff --git a/data/os/suse.com/sle-15-unknown.xml.in > > b/data/os/suse.com/sle-15-unknown.xml.in > > new file mode 100644 > > index 000..7fe318e > > --- /dev/null > > +++ b/data/os/suse.com/sle-15-unknown.xml.in > > @@ -0,0 +1,63 @@ > > + > > + > > + http://suse.com/sle/15;> > > Did you want this to be http://suse.com/sle/15-unknown;> like the > others? Oops, you're right. I'll fix this up before pushing this part of the series. Best Regards and thanks for the review! -- Fabiano Fidêncio ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [PATCH] NetBSD: add NetBSD 7.2 data
Vicente, On Thu, Nov 15, 2018 at 7:15 PM Vicente Chaves de Melo wrote: > > Hello Fabiano, > NetBSD has a very peculiar version numbering. > As described in the https://www.netbsd.org/releases/release-map.html link > > NetBSD 7.2 is the result of the development of the NetBSD-7 branch. > > Therefore, it is derived from 7.0 and is an update of 7.1. Thanks for the clarification :-) I'll push the patches later Today! [snip] ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [osinfo-db PATCH 6/6] suse: Add SLE unknwon info
>>> On 11/5/2018 at 02:05 AM, Fabiano Fidêncio wrote: > In a similar way of what's done on openSUSE and Fedora, let's have an > "unknown" entry for SLE that would cover any possible future releases > while the proper release is not added to our db. > > Signed-off-by: Fabiano Fidêncio > --- > data/os/suse.com/sle-unknown.xml.in | 63 + > 1 file changed, 63 insertions(+) > create mode 100644 data/os/suse.com/sle-unknown.xml.in > > diff --git a/data/os/suse.com/sle-unknown.xml.in > b/data/os/suse.com/sle-unknown.xml.in > new file mode 100644 > index 000..4b3c694 > --- /dev/null > +++ b/data/os/suse.com/sle-unknown.xml.in > @@ -0,0 +1,63 @@ > + > + > + http://suse.com/sle/unknown;> > +sle-unknown > +<_name>SUSE Linux Enterprise Unknown > +unknown > +<_vendor>SUSE > +linux > +sle > +http://suse.com/sle/15"/> > +http://suse.com/sle/15"/> > + > + > + > +LINUX > +SLE-(1[6-9]|[2-9][0-9])-Installer-DVD-x86_64 > + > + boot/x86_64/loader/linux > + boot/x86_64/loader/initrd > + > + > + > + > +LINUX > +SLE-(1[6-9]|[2-9][0-9])-Installer-DVD-aarch64 > + > + boot/aarch64/linux > + boot/aarch64/initrd > + > + > + > + > +LINUX > +SLE-(1[6-9]|[2-9][0-9])-Installer-DVD-ppc64le > + > + boot/ppc64le/linux > + boot/ppc64le/initrd > + > + > + > + > +LINUX > +SLE-(1[6-9]|[2-9][0-9])-Installer-DVD-s390x > + > + boot/s390x/linux > + boot/s390x/initrd > + > + > + > + > +5 > +536870912 > +1074151424 > + > + > +24 > +1073741824 > +17179869184 > + > + > + > + > -- > 2.19.1 Looks good to me. Thanks, - Charles ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [osinfo-db PATCH 4/6] suse: Add SLE[SD]-12-unknown info
>>> On 11/5/2018 at 02:05 AM, Fabiano Fidêncio wrote: > In a similar way of what's done on openSUSE and Fedora, let's have an > "unknown" entry for SLE[SD]-12 that would cover any possible future > release while the proper release is not added to our db. > > Signed-off-by: Fabiano Fidêncio > --- > data/os/suse.com/sled-12-unknown.xml.in | 36 ++ > data/os/suse.com/sles-12-unknown.xml.in | 63 + > 2 files changed, 99 insertions(+) > create mode 100644 data/os/suse.com/sled-12-unknown.xml.in > create mode 100644 data/os/suse.com/sles-12-unknown.xml.in > > diff --git a/data/os/suse.com/sled-12-unknown.xml.in > b/data/os/suse.com/sled-12-unknown.xml.in > new file mode 100644 > index 000..d3fb3bc > --- /dev/null > +++ b/data/os/suse.com/sled-12-unknown.xml.in > @@ -0,0 +1,36 @@ > + > + > + http://suse.com/sled/12-unknown;> > +sled12-unknown > +<_name>SUSE Linux Enterprise Desktop 12 Unknown > +12-unknown > +<_vendor>SUSE > +linux > +sled > +http://suse.com/sled/12.3"/> > +http://suse.com/sled/12.3"/> > + > + > + > +LINUX > +SLE-12-SP[4-9]-Desktop-DVD-x86_64 > + > + boot/x86_64/loader/linux > + boot/x86_64/loader/initrd > + > + > + > + > +5 > +536870912 > +1074151424 > + > + > +24 > +1073741824 > +17179869184 > + > + > + > + > diff --git a/data/os/suse.com/sles-12-unknown.xml.in > b/data/os/suse.com/sles-12-unknown.xml.in > new file mode 100644 > index 000..0b69493 > --- /dev/null > +++ b/data/os/suse.com/sles-12-unknown.xml.in > @@ -0,0 +1,63 @@ > + > + > + http://suse.com/sles/12-unknown;> > +sles12-unknown > +<_name>SUSE Linux Enterprise Server 12 Unknown > +12-unknown > +<_vendor>SUSE > +linux > +sles > +http://suse.com/sles/12.3"/> > +http://suse.com/sles/12.3"/> > + > + > + > +LINUX > +SLE-12-SP[4-9]-Server-DVD-x86_64 > + > + boot/x86_64/loader/linux > + boot/x86_64/loader/initrd > + > + > + > + > +LINUX > +SLE-12-SP[4-9]-Server-DVD-aarch64 > + > + boot/aarch64/linux > + boot/aarch64/initrd > + > + > + > + > +LINUX > +SLE-12-SP[4-9]-Server-DVD-ppc64le > + > + boot/ppc64le/linux > + boot/ppc64le/initrd > + > + > + > + > +LINUX > +SLE-12-SP[4-9]-Server-DVD-s390x > + > + boot/s390x/linux > + boot/s390x/initrd > + > + > + > + > +5 > +536870912 > +1074151424 > + > + > +24 > +1073741824 > +17179869184 > + > + > + > + > -- > 2.19.1 Looks good to me. Thanks, - Charles ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [PATCH] NetBSD: add NetBSD 7.2 data
Hello Fabiano, NetBSD has a very peculiar version numbering. As described in the https://www.netbsd.org/releases/release-map.html link NetBSD 7.2 is the result of the development of the NetBSD-7 branch. Therefore, it is derived from 7.0 and is an update of 7.1. Regards, Vicente. On 15/11/2018 06:36, Fabiano Fidêncio wrote: Vicente, Both patches look good and I'll apply them soon. There's one question though ... On Thu, 2018-11-15 at 00:19 -0200, Vicente Chaves de Melo wrote: --- data/os/netbsd.org/netbsd-7.2.xml.in | 64 1 file changed, 64 insertions(+) create mode 100644 data/os/netbsd.org/netbsd-7.2.xml.in diff --git a/data/os/netbsd.org/netbsd-7.2.xml.in b/data/os/netbsd.org/netbsd-7.2.xml.in new file mode 100644 index 000..0b44e48 --- /dev/null +++ b/data/os/netbsd.org/netbsd-7.2.xml.in @@ -0,0 +1,64 @@ + + + http://netbsd.org/netbsd/7.2;> +netbsd7.2 +<_name>NetBSD 7.2 +7.2 +<_vendor>NetBSD Project +netbsd +netbsd +http://netbsd.org/netbsd/7.1"/> +http://netbsd.org/netbsd/7.0"/> Shouldn't 7.2 upgrade and derive-from 7.1.2? [snip] For both patches: Reviewed-by: Fabiano Fidêncio Thanks for the contributions, ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [libosinfo PATCH] rhel: Add rhel8.0 isodata
Signed-off-by: Fabiano Fidêncio --- .../RHEL-8.0-20181113.1-aarch64-boot.iso.txt | 29 +++ .../RHEL-8.0-20181113.1-aarch64-dvd1.iso.txt | 29 +++ .../RHEL-8.0-20181113.1-ppc64le-boot.iso.txt | 16 ++ .../RHEL-8.0-20181113.1-ppc64le-dvd1.iso.txt | 16 ++ .../RHEL-8.0-20181113.1-s390x-boot.iso.txt| 29 +++ .../RHEL-8.0-20181113.1-s390x-dvd1.iso.txt| 29 +++ .../RHEL-8.0-20181113.1-x86_64-boot.iso.txt | 29 +++ .../RHEL-8.0-20181113.1-x86_64-dvd1.iso.txt | 29 +++ 8 files changed, 206 insertions(+) create mode 100644 tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-aarch64-boot.iso.txt create mode 100644 tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-aarch64-dvd1.iso.txt create mode 100644 tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-ppc64le-boot.iso.txt create mode 100644 tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-ppc64le-dvd1.iso.txt create mode 100644 tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-s390x-boot.iso.txt create mode 100644 tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-s390x-dvd1.iso.txt create mode 100644 tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-x86_64-boot.iso.txt create mode 100644 tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-x86_64-dvd1.iso.txt diff --git a/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-aarch64-boot.iso.txt b/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-aarch64-boot.iso.txt new file mode 100644 index 000..b1b7cba --- /dev/null +++ b/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-aarch64-boot.iso.txt @@ -0,0 +1,29 @@ +CD-ROM is in ISO 9660 format +System id: LINUX +Volume id: RHEL-8-0-BaseOS-aarch64 +Volume set id: +Publisher id: +Data preparer id: +Application id: GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR (C) 1993 E.YOUNGDALE (C) 1997-2006 J.PEARSON/J.SCHILLING (C) 2006-2007 CDRKIT TEAM +Copyright File id: +Abstract File id: +Bibliographic File id: +Volume set size is: 1 +Volume set sequence number is: 1 +Logical block size is: 2048 +Volume size is: 256972 +El Torito VD version 1 found, boot catalog is in sector 42 +Joliet with UCS level 3 found +Rock Ridge signatures version 1 found +Eltorito validation header: +Hid 1 +Arch 239 (Unknown Arch) +ID '' +Key 55 AA +Eltorito defaultboot header: +Bootid 88 (bootable) +Boot media 0 (No Emulation Boot) +Load segment 0 +Sys type 0 +Nsect 32D0 +Bootoff 2C 44 diff --git a/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-aarch64-dvd1.iso.txt b/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-aarch64-dvd1.iso.txt new file mode 100644 index 000..ce01c02 --- /dev/null +++ b/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-aarch64-dvd1.iso.txt @@ -0,0 +1,29 @@ +CD-ROM is in ISO 9660 format +System id: LINUX +Volume id: RHEL-8-0-BaseOS-aarch64 +Volume set id: +Publisher id: +Data preparer id: +Application id: GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR (C) 1993 E.YOUNGDALE (C) 1997-2006 J.PEARSON/J.SCHILLING (C) 2006-2007 CDRKIT TEAM +Copyright File id: +Abstract File id: +Bibliographic File id: +Volume set size is: 1 +Volume set sequence number is: 1 +Logical block size is: 2048 +Volume size is: 2867727 +El Torito VD version 1 found, boot catalog is in sector 847 +Joliet with UCS level 3 found +Rock Ridge signatures version 1 found +Eltorito validation header: +Hid 1 +Arch 239 (Unknown Arch) +ID '' +Key 55 AA +Eltorito defaultboot header: +Bootid 88 (bootable) +Boot media 0 (No Emulation Boot) +Load segment 0 +Sys type 0 +Nsect 32D0 +Bootoff F08 3848 diff --git a/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-ppc64le-boot.iso.txt b/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-ppc64le-boot.iso.txt new file mode 100644 index 000..ccf738a --- /dev/null +++ b/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-ppc64le-boot.iso.txt @@ -0,0 +1,16 @@ +CD-ROM is in ISO 9660 format +System id: PPC +Volume id: RHEL_8_0_BaseOS_ppc64le +Volume set id: 8.0 +Publisher id: +Data preparer id: +Application id: Red Hat Enterprise Linux 8.0 +Copyright File id: +Abstract File id: +Bibliographic File id: +Volume set size is: 1 +Volume set sequence number is: 1 +Logical block size is: 2048 +Volume size is: 279805 +Joliet with UCS level 3 found +Rock Ridge signatures version 1 found diff --git a/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-ppc64le-dvd1.iso.txt b/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-ppc64le-dvd1.iso.txt new file mode 100644 index 000..1eb781b --- /dev/null +++ b/tests/isodata/rhel/rhel8.0/RHEL-8.0-20181113.1-ppc64le-dvd1.iso.txt @@ -0,0 +1,16 @@ +CD-ROM is in ISO 9660 format +System id: PPC +Volume id: RHEL-8-0-BaseOS-ppc64le +Volume set id: +Publisher id: +Data preparer id: +Application id: GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR (C) 1993 E.YOUNGDALE (C) 1997-2006 J.PEARSON/J.SCHILLING (C)
[Libosinfo] [osinfo-db PATCH] rhel: Add rhel8.0 data
https://www.redhat.com/en/blog/powering-its-future-while-preserving-present-introducing-red-hat-enterprise-linux-8-beta Signed-off-by: Fabiano Fidêncio --- data/os/redhat.com/rhel-8.0.xml.in | 77 ++ 1 file changed, 77 insertions(+) create mode 100644 data/os/redhat.com/rhel-8.0.xml.in diff --git a/data/os/redhat.com/rhel-8.0.xml.in b/data/os/redhat.com/rhel-8.0.xml.in new file mode 100644 index 000..5b3648d --- /dev/null +++ b/data/os/redhat.com/rhel-8.0.xml.in @@ -0,0 +1,77 @@ + + + http://redhat.com/rhel/8.0;> +rhel8.0 +<_name>Red Hat Enterprise Linux 8.0 +8.0 +<_vendor>Red Hat, Inc +linux +rhel +http://redhat.com/rhel/7.6"/> + +prerelease + + + +LINUX +RHEL-8-0-BaseOS-x86_64 + + isolinux/vmlinuz + isolinux/initrd.img + + + + +PPC +RHEL[_-]8[_-]0[_-]BaseOS[_-]ppc64le + + ppc/ppc64/vmlinuz + ppc/ppc64/initrd.img + + + + +LINUX +RHEL-8-0-BaseOS-aarch64 + + + + + +LINUX +RHEL-8-0-BaseOS-s390x + + + + + +1 +10 +2147483648 +10737418240 + + + +40 +2147483648 +21474836480 + + + + + +1 +10 +1073741824 +10737418240 + + + +10 +1073741824 +10737418240 + + + + -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [osinfo-db PATCH] popos: Add popos18.10 data
Signed-off-by: Fabiano Fidêncio --- data/os/system76.com/popos-18.10.xml.in | 58 + 1 file changed, 58 insertions(+) create mode 100644 data/os/system76.com/popos-18.10.xml.in diff --git a/data/os/system76.com/popos-18.10.xml.in b/data/os/system76.com/popos-18.10.xml.in new file mode 100644 index 000..a6e8087 --- /dev/null +++ b/data/os/system76.com/popos-18.10.xml.in @@ -0,0 +1,58 @@ + + + http://system76.com/popos/18.10;> +popos18.10 +<_name>Pop!_OS 18.10 +18.10 +<_vendor>System76, Inc. +linux +popos +http://system76.com/popos/18.04"/> +http://system76.com/popos/18.04"/> + +2018-04-30 + + + <_name>Pop!_OS 18.10 (NVIDIA) + + + <_name>Pop!_OS 18.10 (Intel/AMD) + + + + + https://d1vhcvzji58n1j.cloudfront.net/pop-os/iso/18.10/amd64/nvidia/3/pop-os_18.10_amd64_nvidia_3.iso + +Pop_OS 18.10 amd64 +2401763328 + + casper/vmlinuz.efi + casper/initrd.gz + + + + https://d1vhcvzji58n1j.cloudfront.net/pop-os/iso/18.10/amd64/intel/3/pop-os_18.10_amd64_intel_3.iso + +Pop_OS 18.10 amd64 +2145386496 + + casper/vmlinuz.efi + casper/initrd.gz + + + + +10 +1 +1073741824 +5368709120 + + +10 +1073741824 +16106127360 + + + + -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [osinfo-db PATCH] ubuntu18.10: Update data after release
Could you please add a 19.04 daily config now too? The codename is "Disco Dingo" and it is scheduled for release on April 18, 2019. https://wiki.ubuntu.com/DiscoDingo/ReleaseSchedule Thanks, Jeremy Bicha ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [libosinfo] ubuntu18.10: Update isodata after release
Signed-off-by: Fabiano Fidêncio --- .../ubuntu18.10/cosmic-desktop-amd64.iso.txt | 4 +-- .../cosmic-live-server-amd64.iso.txt | 29 +++ .../ubuntu18.10/cosmic-server-amd64.iso.txt | 6 ++-- .../ubuntu18.10/cosmic-server-arm64.iso.txt | 6 ++-- .../ubuntu18.10/cosmic-server-ppc64el.iso.txt | 2 +- .../ubuntu18.10/cosmic-server-s390x.iso.txt | 8 ++--- 6 files changed, 42 insertions(+), 13 deletions(-) create mode 100644 tests/isodata/ubuntu/ubuntu18.10/cosmic-live-server-amd64.iso.txt diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-desktop-amd64.iso.txt b/tests/isodata/ubuntu/ubuntu18.10/cosmic-desktop-amd64.iso.txt index 9f35b22..ad94849 100644 --- a/tests/isodata/ubuntu/ubuntu18.10/cosmic-desktop-amd64.iso.txt +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-desktop-amd64.iso.txt @@ -11,7 +11,7 @@ Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 -Volume size is: 978240 +Volume size is: 976320 El Torito VD version 1 found, boot catalog is in sector 194 Joliet with UCS level 3 found Rock Ridge signatures version 1 found @@ -26,4 +26,4 @@ Eltorito validation header: Load segment 0 Sys type 0 Nsect 4 -Bootoff E99EC 956908 +Bootoff E9066 954470 diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-live-server-amd64.iso.txt b/tests/isodata/ubuntu/ubuntu18.10/cosmic-live-server-amd64.iso.txt new file mode 100644 index 000..7e25c68 --- /dev/null +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-live-server-amd64.iso.txt @@ -0,0 +1,29 @@ +CD-ROM is in ISO 9660 format +System id: +Volume id: Ubuntu-Server 18.10 amd64 +Volume set id: +Publisher id: +Data preparer id: XORRISO-1.2.4 2012.07.20.130001, LIBISOBURN-1.2.4, LIBISOFS-1.2.4, LIBBURN-1.2.4 +Application id: +Copyright File id: +Abstract File id: +Bibliographic File id: +Volume set size is: 1 +Volume set sequence number is: 1 +Logical block size is: 2048 +Volume size is: 451072 +El Torito VD version 1 found, boot catalog is in sector 196 +Joliet with UCS level 3 found +Rock Ridge signatures version 1 found +Eltorito validation header: +Hid 1 +Arch 0 (x86) +ID '' +Key 55 AA +Eltorito defaultboot header: +Bootid 88 (bootable) +Boot media 0 (No Emulation Boot) +Load segment 0 +Sys type 0 +Nsect 4 +Bootoff 68EDF 429791 diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-amd64.iso.txt b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-amd64.iso.txt index 2d45260..3574006 100644 --- a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-amd64.iso.txt +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-amd64.iso.txt @@ -11,8 +11,8 @@ Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 -Volume size is: 370688 -El Torito VD version 1 found, boot catalog is in sector 2125 +Volume size is: 367104 +El Torito VD version 1 found, boot catalog is in sector 2115 Joliet with UCS level 3 found Rock Ridge signatures version 1 found Eltorito validation header: @@ -26,4 +26,4 @@ Eltorito validation header: Load segment 0 Sys type 0 Nsect 4 -Bootoff DEA5 56997 +Bootoff DD43 56643 diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-arm64.iso.txt b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-arm64.iso.txt index 0575849..7729543 100644 --- a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-arm64.iso.txt +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-arm64.iso.txt @@ -11,8 +11,8 @@ Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 -Volume size is: 370519 -El Torito VD version 1 found, boot catalog is in sector 4082 +Volume size is: 368334 +El Torito VD version 1 found, boot catalog is in sector 4058 Joliet with UCS level 3 found Rock Ridge signatures version 1 found Eltorito validation header: @@ -26,4 +26,4 @@ Eltorito validation header: Load segment 0 Sys type 0 Nsect 3C0 -Bootoff 1A17E 106878 +Bootoff 1A245 107077 diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-ppc64el.iso.txt b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-ppc64el.iso.txt index 51e26d1..081c295 100644 --- a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-ppc64el.iso.txt +++ b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-ppc64el.iso.txt @@ -11,7 +11,7 @@ Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 -Volume size is: 398772 +Volume size is: 396150 CD-ROM uses ISO 9660:1999 relaxed format NO Joliet present Rock Ridge signatures version 1 found diff --git a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-s390x.iso.txt b/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-s390x.iso.txt index a70bed6..b26a1e2 100644 --- a/tests/isodata/ubuntu/ubuntu18.10/cosmic-server-s390x.iso.txt +++
[Libosinfo] [osinfo-db PATCH] RFC: schema: Add support to Guest Features
One of the requests that came from KubeVirt is that would be really nice if we could expose Guest supported features. In order to do so, I came up with this *prototype* and I'd like to ask for some review of the schema before I actually start implementing something on libosinfo side. One example of how it'll look like is: device-hotplug cpu-hotplug NUMA >From the start: - features *will* be inrited between OSes, by default. - the feature element has an optional "removed" attribute which, by default, is "false". Is this approach okay? Signed-off-by: Fabiano Fidêncio --- data/schema/osinfo.rng.in | 22 ++ 1 file changed, 22 insertions(+) diff --git a/data/schema/osinfo.rng.in b/data/schema/osinfo.rng.in index 6693391..73d6037 100644 --- a/data/schema/osinfo.rng.in +++ b/data/schema/osinfo.rng.in @@ -518,6 +518,25 @@ + + + + + +cpu-hotplug +device-hotplug +NUMA + + + + + + + + + + + @@ -549,6 +568,9 @@ + + + -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
[Libosinfo] [osinfo-db PATCH] debian: Update URLs to 9.6.0
Signed-off-by: Fabiano Fidêncio --- data/os/debian.org/debian-9.xml.in | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/data/os/debian.org/debian-9.xml.in b/data/os/debian.org/debian-9.xml.in index e98690d..53f9e6c 100644 --- a/data/os/debian.org/debian-9.xml.in +++ b/data/os/debian.org/debian-9.xml.in @@ -52,7 +52,7 @@ - http://cdimage.debian.org/cdimage/archive/9.4.0/i386/iso-cd/debian-9.4.0-i386-netinst.iso + http://cdimage.debian.org/cdimage/archive/9.6.0/i386/iso-cd/debian-9.6.0-i386-netinst.iso Debian 9.(\d)+.(\d)+ i386 n @@ -61,7 +61,7 @@ - http://cdimage.debian.org/cdimage/archive/9.4.0/amd64/iso-cd/debian-9.4.0-amd64-netinst.iso + http://cdimage.debian.org/cdimage/archive/9.6.0/amd64/iso-cd/debian-9.6.0-amd64-netinst.iso Debian 9.(\d)+.(\d)+ amd64 n @@ -70,7 +70,7 @@ - http://cdimage.debian.org/cdimage/archive/9.4.0/arm64/iso-cd/debian-9.4.0-arm64-netinst.iso + http://cdimage.debian.org/cdimage/archive/9.6.0/arm64/iso-cd/debian-9.6.0-arm64-netinst.iso Debian 9.(\d)+.(\d)+ arm64 n @@ -79,7 +79,7 @@ - http://cdimage.debian.org/cdimage/archive/9.4.0/armhf/iso-cd/debian-9.4.0-armhf-netinst.iso + http://cdimage.debian.org/cdimage/archive/9.6.0/armhf/iso-cd/debian-9.6.0-armhf-netinst.iso Debian 9.(\d)+.(\d)+ armhf n @@ -90,7 +90,7 @@ - http://cdimage.debian.org/cdimage/archive/9.4.0/i386/iso-dvd/debian-9.4.0-i386-DVD-1.iso + http://cdimage.debian.org/cdimage/archive/9.6.0/i386/iso-dvd/debian-9.6.0-i386-DVD-1.iso Debian 9.(\d)+.(\d)+ i386 1 @@ -99,7 +99,7 @@ - http://cdimage.debian.org/cdimage/archive/9.4.0/amd64/iso-dvd/debian-9.4.0-amd64-DVD-1.iso + http://cdimage.debian.org/cdimage/archive/9.6.0/amd64/iso-dvd/debian-9.6.0-amd64-DVD-1.iso Debian 9.(\d)+.(\d)+ amd64 1 @@ -108,7 +108,7 @@ - http://cdimage.debian.org/cdimage/archive/9.4.0/arm64/iso-dvd/debian-9.4.0-arm64-DVD-1.iso + http://cdimage.debian.org/cdimage/archive/9.6.0/arm64/iso-dvd/debian-9.6.0-arm64-DVD-1.iso Debian 9.(\d)+.(\d)+ arm64 1 @@ -117,7 +117,7 @@ - http://cdimage.debian.org/cdimage/archive/9.4.0/armhf/iso-dvd/debian-9.4.0-armhf-DVD-1.iso + http://cdimage.debian.org/cdimage/archive/9.6.0/armhf/iso-dvd/debian-9.6.0-armhf-DVD-1.iso Debian 9.(\d)+.(\d)+ armhf 1 -- 2.19.1 ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [osinfo-db PATCH 0/6] Add "unknown" entries for Enterprise distros
On Mon, 2018-11-05 at 10:05 +0100, Fabiano Fidêncio wrote: > Although new releases are always patched downstream to support > themselves, upstream is always behind as the new (or in development) > releases will only be part of osinfo-db after they are released. > > One way to solve this issue is adding support to "unknown" entries, > in > the same way we have for Fedora and openSUSE, and make the new (or in > development) release be at least recoginzed and have the proper > devices > loaded for those who are using them in any distro. Charles, may I get your input in the SUSE's related part of this series? Shall I also add an entry for CaaS Platform as well? Daniel, we have discussed this internally and you were fine with the proposed changes. But may I get your ack for the Red Hat's related part of this series? Best Regards, -- Fabiano Fidêncio ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [osinfo-db-tools PATCH 1/1] import: Introduce "--latest" option
Daniel, On Tue, 2018-10-09 at 16:34 +0200, Fabiano Fidêncio wrote: > --latest option checks whether there's a new osinfo-db available from > the official libosinfo's release website, downloads and install it. > > The download and installation is only then when the version available > in > libosinfo's release website is newer than the version installed in > the > (specified location in) system. We have discussed this one during the "BoF" that happened during KVM Forum. Is this code fine by you? Considering it is, would be possible to have something like latest.libosinfo.org (or similar) where we could fetch the info from? [snip] Best Regards, -- Fabiano Fidêncio ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
Re: [Libosinfo] [PATCH] NetBSD: add NetBSD 7.2 data
Vicente, Both patches look good and I'll apply them soon. There's one question though ... On Thu, 2018-11-15 at 00:19 -0200, Vicente Chaves de Melo wrote: > --- > data/os/netbsd.org/netbsd-7.2.xml.in | 64 > > 1 file changed, 64 insertions(+) > create mode 100644 data/os/netbsd.org/netbsd-7.2.xml.in > > diff --git a/data/os/netbsd.org/netbsd-7.2.xml.in > b/data/os/netbsd.org/netbsd-7.2.xml.in > new file mode 100644 > index 000..0b44e48 > --- /dev/null > +++ b/data/os/netbsd.org/netbsd-7.2.xml.in > @@ -0,0 +1,64 @@ > + > + > + http://netbsd.org/netbsd/7.2;> > +netbsd7.2 > +<_name>NetBSD 7.2 > +7.2 > +<_vendor>NetBSD Project > +netbsd > +netbsd > +http://netbsd.org/netbsd/7.1"/> > +http://netbsd.org/netbsd/7.0"/> Shouldn't 7.2 upgrade and derive-from 7.1.2? [snip] For both patches: Reviewed-by: Fabiano Fidêncio Thanks for the contributions, -- Fabiano Fidêncio ___ Libosinfo mailing list Libosinfo@redhat.com https://www.redhat.com/mailman/listinfo/libosinfo
