trunk : Code : libosinfo

Get this branch:: bzr branch lp:libosinfo

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related bugs

Link a bug report

Related blueprints

Branch information

Owner:: Registry Administrators

Project:: libosinfo

Status:: Development

Import details

Import Status: Failed

This branch is an import of the HEAD branch of the Git repository at git://git.fedorahosted.org/libosinfo.git.

The import has been suspended because it failed 5 or more times in succession.

Last successful import was on 2017-03-01.

Import started on 2017-03-05 on pear and finished on 2017-03-05 taking 20 seconds — see the log

Import started on 2017-03-03 on pear and finished on 2017-03-03 taking 20 seconds — see the log

Import started on 2017-03-02 on pear and finished on 2017-03-02 taking 15 seconds — see the log

Recent revisions

1062. By Daniel Berrange on 2016-03-03

Remove all files and add pointer to new git repostory location

1061. By Roman Bogorodskiy on 2016-03-03

Fix build with older GCC

Build with older gcc fails with:

  CC libosinfo_1_0_la-osinfo_avatar_format.lo
In file included from ../osinfo/osinfo_os.h:30,
                 from ../osinfo/osinfo.h:55,
                 from osinfo_avatar_format.c:28:
../osinfo/osinfo_media.h:68: error: redefinition of typedef 'OsinfoMedia'
../osinfo/osinfo_install_script.h:43: error: previous declaration of 'OsinfoMedia' was here

To avoid redefinition, use forward-declaration in a similar way
like it's done for OsinfoOs in osinfo/osinfo_os.h.

1060. By Guido Günther on 2016-02-05

Update CD URLs to latest Debian Jessie point release

1059. By Fabiano Fidencio on 2016-01-21

build: Fix .vapi generation

After a267020e272a generation of the .vapi file broke. It no longer has
path_pattern property while get_path_pattern() is still there.
Adding nodist_libosinfo_1_0_include_HEADERS to the list of the files
passed to the .gir generation solves the problem.

1058. By Daniel Berrange on 2016-01-13

don't include autogenerated enum files in dist

Previous commit 77cf2730eb6e5503a9bd40e6baf7cc0b393a9dc7
reverts 4e488678d4af0e54da7400851d554bc4c4497c76 (fixes
to the VPATH build) because it was said to break the
make distcheck.

After examining the problem, it seems this commit was not
in fact the problem - it merely exposed the existing bug
elsewhere.

The real problem is that we were including the autogenerated
enum files in the dist. So when doing builds from git those
files were in $builddir, but when doing builds from dist
those files were in $srcdir. Except that 'make distclean'
would delete the enum files, which would again cause them
to appear in $builddir.

So the real fix is stop including the enum files in the dist