headers
Richard Hughes | 5 Sep 2011 15:44
Picon

PackageKit 0.6.18 released!

Version 0.6.18
~~~~~~~~~~~~~~
Released: 2011-09-05

Notes:
 - This update is suitable for stable distros and does not introduce new
   functionality.
 - If you want your dose of insanity, PackageKit 0.7.0 contains lots of
   exciting new code that needs testing.

Libraries:
 - glib: Fix a small memory leak (Garrett Regier)
 - qt: Do not dist the moc files (Richard Hughes)

Backends:
 - aptcc: Fix the size by emitting installed and download size (Daniel
Nicoletti)
 - yum: Ignore missing obsoleted updates rather than failing the
update (Richard Hughes)
 - zif: Fix a fatal error when doing 'pkcon repo-list --filter=~devel'
(Richard Hughes)

Bugfixes:
 - Fix the browser-plugin build with GTK+ < 2.24 (Frederic Crozat)
 - Make the lsof plugin code support distros with /lib64 (Richard Hughes)
 - Make the lsof plugin not lookup hostnames (Richard Hughes)
 - Remove the duplicate 'The software is not from a trusted source'
(Richard Hughes)

Tarballs available here: http://www.packagekit.org/releases/
(Continue reading)

Permalink | Reply | 10 comments |
headers
Fabio Erculiani | 5 Sep 2011 16:58
Favicon
Gravatar

Re: PackageKit 0.6.18 released!

Where did my commit 5d6419ac83883e4d2161032f65d565df8eb007ac go? It's
not in 0.6.18.
I guess there have been workflow changes but I can't find anything on
this mailing list about it.

Care to explain?

Thanks,
--

-- 
Fabio Erculiani
Permalink | Reply | 9 comments |
headers
Richard Hughes | 5 Sep 2011 17:04
Picon

Re: PackageKit 0.6.18 released!

On 5 September 2011 15:58, Fabio Erculiani <lxnay@...> wrote:
> Where did my commit 5d6419ac83883e4d2161032f65d565df8eb007ac go? It's
> not in 0.6.18.
> I guess there have been workflow changes but I can't find anything on
> this mailing list about it.
> Care to explain?

Did you cherry-pick the commit into PACKAGEKIT_0_6_X ?

When we created the PACKAGEKIT_0_6_X branch all the commits to master
just stay on master, and you have to explicitly pick commits into the
new stable branch.

Do do this you need to do:

git branch --track PACKAGEKIT_0_6_X origin/PACKAGEKIT_0_6_X
git checkout PACKAGEKIT_0_6_X
git cherry-pick 5d6419ac83883e4d2161032f65d565df8eb007ac
git push
git checkout master

Sorry if this wasn't communicated very well.

Richard.
Permalink | Reply | 8 comments |
headers
Richard Hughes | 5 Sep 2011 17:58
Picon

PackageKit 0.7.0 released!

Version 0.7.0
~~~~~~~~~~~~~
Released: 2011-09-05

Notes:
 - This is the first release of the unstable 0.7.x series.
 - This code removes a lot of deprecated code and compatibility shims
   compared to the previous branch.
 - Highlights of this release is the new transaction plugin interface
   that allows external projects to add modules for interfacing with
   PackageKit. This allows projects such as Listaller to interface with
   PackageKit to install self contained software blobs.
   See http://listaller.tenstral.net/ for more information.
 - The daemon code is now using GDBus rather than dbus-glib, but the
   libpackagekit-glib library is still using the latter. It'll be
   converted hopefully in time for 0.7.1.
 - It's probably not a good idea to use releases from this branch for
   stable distros or enterprise products!

Libraries:
 - glib: Free the PkProgress' package (Garrett Regier)
 - glib: Remove the foo_from_text() compatibility defines (Richard Hughes)
 - python: Remove the native python library (Richard Hughes)
 - qt2: Use cmake package config instead of Find* module (Matthias Klumpp)
 - qt: Do not dist the moc files (Richard Hughes)

Backends:
 - aptcc: Fix crash when long description blow char buffer (Daniel Nicoletti)
 - aptcc: Fix the size by emitting installed and download size (Daniel
Nicoletti)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Fabio Erculiani | 5 Sep 2011 18:02
Favicon
Gravatar

Re: PackageKit 0.6.18 released!

On Mon, Sep 5, 2011 at 5:04 PM, Richard Hughes <hughsient@...> wrote:
> On 5 September 2011 15:58, Fabio Erculiani <lxnay@...> wrote:
>> Where did my commit 5d6419ac83883e4d2161032f65d565df8eb007ac go? It's
>> not in 0.6.18.
>> I guess there have been workflow changes but I can't find anything on
>> this mailing list about it.
>> Care to explain?
>
> Did you cherry-pick the commit into PACKAGEKIT_0_6_X ?

How could I know that ;-)

>
> When we created the PACKAGEKIT_0_6_X branch all the commits to master
> just stay on master, and you have to explicitly pick commits into the
> new stable branch.
>
> Do do this you need to do:
>
> git branch --track PACKAGEKIT_0_6_X origin/PACKAGEKIT_0_6_X
> git checkout PACKAGEKIT_0_6_X

Nowadays, you just need:
git checkout PACKAGEKIT_0_6_X

> git cherry-pick 5d6419ac83883e4d2161032f65d565df8eb007ac
> git push

Done, thanks
(Continue reading)

Permalink | Reply | 7 comments |
headers
Richard Hughes | 5 Sep 2011 18:05
Picon

Re: PackageKit 0.6.18 released!

On 5 September 2011 17:02, Fabio Erculiani <lxnay@...> wrote:
> How could I know that ;-)

We had a "when shall we branch" email discussion a few months ago, but
maybe that slipped under your radar. No worries, as you're not the
only one affected. :-)

> Nowadays, you just need:
> git checkout PACKAGEKIT_0_6_X

Yup, Daniel has a really old version of git, so I did it old-skool.

> Done, thanks

Great. We'll have a new stable release in a few weeks for the entropy
and aptcc fixes.

Richard.
Permalink | Reply | 0 comments |
headers
Daniel Nicoletti | 5 Sep 2011 18:05
Picon
Favicon

Re: PackageKit 0.6.18 released!

>> Do do this you need to do:
>>
>> git branch --track PACKAGEKIT_0_6_X origin/PACKAGEKIT_0_6_X
>> git checkout PACKAGEKIT_0_6_X
>
>Nowadays, you just need:
>git checkout PACKAGEKIT_0_6_X

This is since when? I'm using git 1.7.4.1 and that
didn't work here ...
Permalink | Reply | 5 comments |
headers
Fabio Erculiani | 5 Sep 2011 18:11
Favicon
Gravatar

Re: PackageKit 0.6.18 released!

On Mon, Sep 5, 2011 at 6:05 PM, Daniel Nicoletti
<daniel_nic85@...> wrote:
>>> Do do this you need to do:
>>>
>>> git branch --track PACKAGEKIT_0_6_X origin/PACKAGEKIT_0_6_X
>>> git checkout PACKAGEKIT_0_6_X
>>
>>Nowadays, you just need:
>>git checkout PACKAGEKIT_0_6_X
>
>
> This is since when? I'm using git 1.7.4.1 and that
> didn't work here ...

OLD!
git 1.7.6 bleeding edgeness ftw

;-)

--

-- 
Fabio Erculiani
Permalink | Reply | 4 comments |
headers
Fabio Erculiani | 5 Sep 2011 22:22
Favicon
Gravatar

Re: PackageKit 0.6.18 released!

Moreover:
/bin/sh ../../../libtool --silent --tag=CXX   --mode=compile
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../../.. -DQT_SHARED
-I/usr/include/qt4 -I/usr/include/qt4/QtCore   -DQT_SHARED
-I/usr/include/qt4 -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtXml   -DQT_SHARED -I/usr/include/qt4
-I/usr/include/qt4/QtSql -I/usr/include/qt4/QtCore
-DLOCALSTATEDIR=\""/var"\"
-DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\"    -O2 -march=x86-64
-pipe -c -o client.lo client.cpp
In file included from client.cpp:586:0:
client.moc:13:2: error: #error "This file was generated using the moc
from 4.8.0. It"
client.moc:14:2: error: #error "cannot be used with the include files
from this version of Qt."
client.moc:15:2: error: #error "(The moc has changed too much.)"
client.moc:74:98: error: no ‘void
PackageKit::Client::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**)’ member function declared in class ‘PackageKit::Client’
client.moc:91:48: error: ‘const QMetaObjectExtraData
PackageKit::Client::staticMetaObjectExtraData’ is not a static member
of ‘class PackageKit::Client’
client.moc:92:9: error: ‘qt_static_metacall’ was not declared in this scope
client.moc:97:41: error: ‘staticMetaObjectExtraData’ was not declared
in this scope
client.moc: In member function ‘virtual int
PackageKit::Client::qt_metacall(QMetaObject::Call, int, void**)’:
client.moc:124:49: error: ‘qt_static_metacall’ was not declared in this scope
make[2]: *** [client.lo] Errore 1
make[2]: Leaving directory
(Continue reading)

Permalink | Reply | 3 comments |
headers
Fabio Erculiani | 5 Sep 2011 22:25
Favicon
Gravatar

Re: PackageKit 0.6.18 released!

The .moc files should be removed from the tarball.
The build system will re-generate them.

Thanks,
--

-- 
Fabio Erculiani
Permalink | Reply | 2 comments |

Gmane