Hello all,
openSUSE 12.1 Milestone 4 will be released next week, on Thursday 11 August 2011.
Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday.
For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap
Thanks,
Am Wed, 3 Aug 2011 08:00:02 +0200 (CEST) schrieb openSUSE Roadmap Reminder vuntz@opensuse.org:
Hello all,
openSUSE 12.1 Milestone 4 will be released next week, on Thursday 11 August 2011.
Unfortunately, testing is impossible:
seife@susi:~/buildservice/testing/bluez> osc build --ccache Building bluez.spec for openSUSE_Factory/x86_64 Getting buildinfo from server and store to /local/buildservice/home:seife/home:seife:testing/bluez/.osc/_buildinfo-openSUSE_Factory-x86_64.xml Getting buildconfig from server and store to /local/buildservice/home:seife/home:seife:testing/bluez/.osc/_buildconfig-openSUSE_Factory-x86_64 Updating cache of required packages 0.0% cache miss. 158/158 dependencies cached.
Verifying integrity of cached packages using keys from openSUSE:Factory /local/osbuild-packagecache/openSUSE:Factory/_pubkey :failed to import pubkey Traceback (most recent call last): File "/usr/bin/osc", line 21, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 52, in run return prg.main() File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 310, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 333, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 449, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1179, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 4945, in do_build return osc.build.main(self.get_api_url(), opts, args) File "/usr/lib/python2.7/site-packages/osc/build.py", line 771, in main verify_pacs(bi) File "/usr/lib/python2.7/site-packages/osc/fetch.py", line 346, in verify_pacs checker.readkeys(bi.keys) File "/usr/lib/python2.7/site-packages/osc/checker.py", line 35, in readkeys raise KeyError('', "no key imported") osc.checker.KeyError: :no key imported seife@susi:~/buildservice/testing/bluez> osc r openSUSE_11.3 i586 disabled openSUSE_11.3 x86_64 disabled openSUSE_11.4 x86_64 disabled openSUSE_11.4 i586 disabled openSUSE_Factory i586 failed openSUSE_Factory x86_64 failed openSUSE_Tumbleweed x86_64 failed openSUSE_Tumbleweed i586 failed SLE-11_SP1 x86_64 disabled seife@susi:~/buildservice/testing/bluez> osc bl openSUSE_Factory x86_64 | grep -A 10 "RPM build errors" RPM build errors: File not found: /usr/src/packages/BUILDROOT/bluez-4.96-104.2.x86_64/lib/systemd/system/bluetooth.service Installed (but unpackaged) file(s) found: /usr/bin/apitest /usr/bin/dund /usr/bin/l2test /usr/bin/list-devices /usr/bin/pand /usr/bin/rctest /usr/bin/simple-agent /usr/bin/simple-service
Please submit your packages before Friday afternoon (UTC time) to make
Should we really submit untested packages?
On 08/04/2011 01:38 PM, Stefan Seyfried wrote:
Am Wed, 3 Aug 2011 08:00:02 +0200 (CEST) schrieb openSUSE Roadmap Remindervuntz@opensuse.org:
Hello all,
openSUSE 12.1 Milestone 4 will be released next week, on Thursday 11 August 2011.
Unfortunately, testing is impossible:
seife@susi:~/buildservice/testing/bluez> osc build --ccache Building bluez.spec for openSUSE_Factory/x86_64 Getting buildinfo from server and store to /local/buildservice/home:seife/home:seife:testing/bluez/.osc/_buildinfo-openSUSE_Factory-x86_64.xml Getting buildconfig from server and store to /local/buildservice/home:seife/home:seife:testing/bluez/.osc/_buildconfig-openSUSE_Factory-x86_64 Updating cache of required packages 0.0% cache miss. 158/158 dependencies cached.
Verifying integrity of cached packages using keys from openSUSE:Factory /local/osbuild-packagecache/openSUSE:Factory/_pubkey :failed to import pubkey
For now please workaround with osc build --no-verify , there is something wrong with rpm's python api.
Regards.
Am Thu, 04 Aug 2011 13:40:35 +0200 schrieb Ismail Donmez idoenmez@suse.de:
For now please workaround with osc build --no-verify , there is something wrong with rpm's python api.
No, setting up a throwaway VM just for building packages is too much work directly before vacation. Someone just fix the buildservice so that it will actually build packages again, that will be enough for testing. (home:seife:testing/bluez is failing for purely BS reasons - nothing changed in the specfile which could trigger the fail)
On Thu, Aug 04, 2011 at 01:44:36PM +0200, Stefan Seyfried wrote:
Am Thu, 04 Aug 2011 13:40:35 +0200 schrieb Ismail Donmez idoenmez@suse.de:
For now please workaround with osc build --no-verify , there is something wrong with rpm's python api.
No, setting up a throwaway VM just for building packages is too much work directly before vacation. Someone just fix the buildservice so that it will actually build packages again, that will be enough for testing. (home:seife:testing/bluez is failing for purely BS reasons - nothing changed in the specfile which could trigger the fail)
/lib/systemd/system/bluetooth.service is missing. It is generated, but apparently "make install" does not want to install it.
Ciao, Marcus
Am Donnerstag, 4. August 2011 schrieb Stefan Seyfried:
Am Thu, 04 Aug 2011 13:40:35 +0200
schrieb Ismail Donmez idoenmez@suse.de:
For now please workaround with osc build --no-verify , there is something wrong with rpm's python api.
No, setting up a throwaway VM just for building packages is too much work directly before vacation. Someone just fix the buildservice so that it will actually build packages again, that will be enough for testing. (home:seife:testing/bluez is failing for purely BS reasons - nothing changed in the specfile which could trigger the fail)
Nothing changed? Just the version number you mean?
Greetings, Stephan
Am Thu, 4 Aug 2011 13:47:23 +0200 schrieb Marcus Meissner meissner@suse.de:
On Thu, Aug 04, 2011 at 01:44:36PM +0200, Stefan Seyfried wrote:
Am Thu, 04 Aug 2011 13:40:35 +0200 schrieb Ismail Donmez idoenmez@suse.de:
For now please workaround with osc build --no-verify , there is something wrong with rpm's python api.
No, setting up a throwaway VM just for building packages is too much work directly before vacation. Someone just fix the buildservice so that it will actually build packages again, that will be enough for testing. (home:seife:testing/bluez is failing for purely BS reasons - nothing changed in the specfile which could trigger the fail)
/lib/systemd/system/bluetooth.service is missing. It is generated, but apparently "make install" does not want to install it.
But this does not have anything to do with the build errors, does it? And it does not explain why 11.4, Tumbleweed etc. build well (after disabling stupid rpmlint or whatever checks).
Am Thu, 4 Aug 2011 13:53:06 +0200 schrieb Stephan Kulow coolo@suse.de:
Nothing changed? Just the version number you mean?
It built well yesterday, it was just not published because something was hanging in buildservice. Today I triggered a rebuild and it fails. Not even the version number changed.
Am Thu, 4 Aug 2011 14:45:29 +0200 schrieb Stefan Seyfried stefan.seyfried@googlemail.com:
Am Thu, 4 Aug 2011 13:53:06 +0200 schrieb Stephan Kulow coolo@suse.de:
Nothing changed? Just the version number you mean?
It built well yesterday, it was just not published because something was hanging in buildservice. Today I triggered a rebuild and it fails. Not even the version number changed.
HAHA! systemd grew a devel package overnight... slap them systemd packagers with a cluestick, please for incompatible changes without announcement...
Le jeudi 04 août 2011, à 14:52 +0200, Stefan Seyfried a écrit :
Am Thu, 4 Aug 2011 14:45:29 +0200 schrieb Stefan Seyfried stefan.seyfried@googlemail.com:
Am Thu, 4 Aug 2011 13:53:06 +0200 schrieb Stephan Kulow coolo@suse.de:
Nothing changed? Just the version number you mean?
It built well yesterday, it was just not published because something was hanging in buildservice. Today I triggered a rebuild and it fails. Not even the version number changed.
HAHA! systemd grew a devel package overnight... slap them systemd packagers with a cluestick, please for incompatible changes without announcement...
Or you could use pkgconfig(systemd) as BuildRequires.
Vincent
Am Thu, 4 Aug 2011 14:57:44 +0200 schrieb Vincent Untz vuntz@opensuse.org:
Or you could use pkgconfig(systemd) as BuildRequires.
and break build on anything not bleeding edge?
Le jeudi 04 août 2011, à 18:35 +0200, Stefan Seyfried a écrit :
Am Thu, 4 Aug 2011 14:57:44 +0200 schrieb Vincent Untz vuntz@opensuse.org:
Or you could use pkgconfig(systemd) as BuildRequires.
and break build on anything not bleeding edge?
Can you elaborate on how changing:
%if 0%{?suse_version} > 1130 BuildRequires: systemd-devel %endif
to
%if 0%{?suse_version} > 1130 BuildRequires: pkgconfig(systemd) %endif
breaks anything not bleeding edge?
Vincent
Am Thu, 4 Aug 2011 18:48:49 +0200 schrieb Vincent Untz vuntz@opensuse.org:
Le jeudi 04 août 2011, à 18:35 +0200, Stefan Seyfried a écrit :
and break build on anything not bleeding edge?
Can you elaborate on how changing:
%if 0%{?suse_version} > 1130 BuildRequires: systemd-devel %endif
to
%if 0%{?suse_version} > 1130 BuildRequires: pkgconfig(systemd) %endif
breaks anything not bleeding edge?
Hum, right. And since the braindead "linked against /usr" check breaks it anyway for anything !FACTORY (even tumbleweed), that's probably the thing I'll do for the next version update.
OTOH, bluez does not need the pkgconfig file, so the requires is bogus. It needs only the directory for the service file ;-P
On Thursday, August 04, 2011 14:52:55 Stefan Seyfried wrote:
Am Thu, 4 Aug 2011 14:45:29 +0200
schrieb Stefan Seyfried stefan.seyfried@googlemail.com:
Am Thu, 4 Aug 2011 13:53:06 +0200
schrieb Stephan Kulow coolo@suse.de:
Nothing changed? Just the version number you mean?
It built well yesterday, it was just not published because something was hanging in buildservice. Today I triggered a rebuild and it fails. Not even the version number changed.
HAHA! systemd grew a devel package overnight... slap them systemd packagers with a cluestick, please for incompatible changes without announcement...
Sorry, my fault - ok, I'll write up something now,
Andreas
-
Andreas Jaeger -
Ismail Donmez -
Marcus Meissner -
openSUSE Roadmap Reminder -
Stefan Seyfried -
Stephan Kulow -
Vincent Untz