11 May
2015
11 May
'15
22:36
Hi,
it seems that there is a build dependency missing between kernel and
device tree meta packages:
Logs taken from (build today afternoon):
https://build.opensuse.org/package/binary/home:frank_kunz:branches:openSUSE…
contains up to date kernel:
kernel-default|(none)|4.0.1|1.1|armv7hl|obs://build.opensuse.org/openSUSE:F…
But the device tree is still the old one:
dtb-sun4i|(none)|4.0.0|40.2|armv7hl|obs://build.opensuse.org/openSUSE:Facto…
Br,
Frank
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
12 May
12 May
00:54
Hi,
Am 11.05.2015 um 17:36 schrieb Frank Kunz:
it seems that there is a build dependency missing
between kernel and
device tree meta packages:
Logs taken from (build today afternoon):
https://build.opensuse.org/package/binary/home:frank_kunz:branches:openSUSE…
contains up to date kernel:
kernel-default|(none)|4.0.1|1.1|armv7hl|obs://build.opensuse.org/openSUSE:F…
But the device tree is still the old one:
dtb-sun4i|(none)|4.0.0|40.2|armv7hl|obs://build.opensuse.org/openSUSE:Facto…
There is in fact a "BuildRequires: kernel-source", which should in
theory trigger a rebuild once kernel-source is updated.
https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM/dtb-sourc…
I wondered whether there might simply be no difference between 4.0.0 and
4.0.1 for dtb-sun4i, but the build log does not indicate such a cleanup,
the last build was indeed a 4.0.0 one:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/dtb-…
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
01:30
Andreas Färber <afaerber(a)suse.de> writes:
There is in fact a "BuildRequires:
kernel-source", which should in
theory trigger a rebuild once kernel-source is updated.
No, only new sources trigger a rebuild.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab(a)suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
04:13
Hi Andreas,
Not true either. Any change that causes a package to become
uninstallable which was previously in "succeeded" state will be
automatically rebuild.
Greetings,
Dirk
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
There is in
fact a "BuildRequires: kernel-source", which should in
theory trigger a rebuild once kernel-source is updated.
No, only new sources
trigger a rebuild.
13:39
Dirk Müller <dirk(a)dmllr.de> writes:
Not true either. Any change that causes a package to
become
uninstallable which was previously in "succeeded" state will be
automatically rebuild.
But that's outside the system.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab(a)suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
02:01
Am 11.05.2015 um 19:54 schrieb Andreas Färber:
I wondered whether there might simply be no difference
between 4.0.0 and
4.0.1 for dtb-sun4i, but the build log does not indicate such a cleanup,
the last build was indeed a 4.0.0 one:
The dtb-sun4i is not really affected, it was just the newest image that
I have. But images with dtb-sun5i are not booting with the outdated dtb
files.
Br,
Frank
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
04:12
Hi Frank,
The dtb-sun4i is not really affected, it was just the
newest image that
I have. But images with dtb-sun5i are not booting with the outdated dtb
files.
Should be fixed relatively soon (new packages have already been build,
just publishing takes hours as usual).
The dependency between those two packages is not easy, my previous
attempt at adding requires makes it difficult to upgrade packages or
use multiversion, so I reverted that. Instead I added a hack to the
auto-rebuilder that will rebuild dtb-armv7l when the version numbers
don't match. hopefully noone changes the way dtb-source works
meanwhile.
Greetings,
Dirk
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
17 May
17 May
20:59
Am 11.05.2015 um 23:12 schrieb Dirk Müller:
Should be fixed relatively soon (new packages have
already been build,
just publishing takes hours as usual).
The dependency between those two packages is not easy, my previous
attempt at adding requires makes it difficult to upgrade packages or
use multiversion, so I reverted that. Instead I added a hack to the
auto-rebuilder that will rebuild dtb-armv7l when the version numbers
don't match. hopefully noone changes the way dtb-source works
meanwhile.
Unfortunately the situation is still the same. A zypper ref, zypper up
installs kernel 4.0.3, but the device tree blobs in the repository are
still 4.0.1, so they were not rebuild.
Br,
Frank
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
29 May
29 May
00:59
Hi Frank,
Unfortunately the situation is still the same. A
zypper ref, zypper up
installs kernel 4.0.3, but the device tree blobs in the repository are
still 4.0.1, so they were not rebuild.
Right, there was a typo in the script. Fixed now...
Thanks,
Dirk
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
2217
days inactive
2234
days old
8 comments
4 participants
participants (4)
-
Andreas Färber -
Andreas Schwab -
Dirk Müller -
Frank Kunz