6:29 p.m.
Hi!
I was a bit rude earlier today and without any warning removed a few
packages from the devel repos (that just became the F15 release repos)
due to broken deps. See the list below for details; would be good if
anybody would tell the maintainers directly, but I don't care about RPM
Fusion enough these days to file bugs myself. Of course all of them can
simply be reintroduced by building a update.
Cu
thl
= Free =
compat-{plone,zope,python24*} (not build in ages for devel)
autopano-sift-C-2.5.1-3.fc14.src.rpm
elisa-plugins-ugly-0.5.35-1.fc11.src.rpm
pragha-0.8.2-1.fc14.src.rpm
sonic-visualiser-freeworld-1.7.1-1.fc13.src.rpm
vdr-dxr3-0.2.10-3.fc14.src.rpm (depends on kmod-em8300 that doesn't
build for FC15)
west-chamber* xtables-addons* -- xtables-addons-kmod (required by
west-chamber) does not build in F15
open-vm-tools-kmod -- open-vm-tools does not build on F15
package: autopano-sift-C-2.5.1-3.fc14.x86_64 from rpmfusion-free-rawhide
unresolved deps:
libpano13.so.1()(64bit)
compat-python24-libxml2-2.7.6-1.fc12.x86_64 from rpmfusion-free-rawhide
unresolved deps:
libxml2 = 0:2.7.6
package: elisa-plugins-ugly-0.5.35-1.fc11.noarch from rpmfusion-free-rawhide
unresolved deps:
python(abi) = 0:2.6
package: pragha-0.8.2-1.fc14.x86_64 from rpmfusion-free-rawhide
unresolved deps:
libnotify.so.1()(64bit)
package: sonic-visualiser-freeworld-1.7.1-1.fc13.x86_64 from
rpmfusion-free-rawhide
unresolved deps:
liboggz.so.1()(64bit)
liblo.so.0()(64bit)
liboggz.so.1(liboggz.so.0.2)(64bit)
package: vdr-dxr3-0.2.10-3.fc14.x86_64 from rpmfusion-free-rawhide
unresolved deps:
em8300-kmod >= 0:0.15.2
package: akmod-open-vm-tools-0.0.0.301124-2.fc15.x86_64 from
rpmfusion-free-rawhide
unresolved deps:
open-vm-tools-kmod-common >= 0:0.0.0.301124
= Nonfree =
ec2-api-tools-1.4.2.4-1.fc15.src.rpm
frogatto-1.0.3-2.fc14.src.rpm
ogre-cg-1.6.1-4.fc12.src.rpm
pdflib-lite-7.0.5-1.fc14.src.rpm and
php-pecl-pdflib-2.1.8-1.fc14.src.rpm that depends on it
package: ec2-api-tools-1.4.2.4-1.fc15.noarch from rpmfusion-nonfree-rawhide
unresolved deps:
jaf
package: frogatto-1.0.3-2.fc14.x86_64 from rpmfusion-nonfree-rawhide
unresolved deps:
libboost_system-mt.so.1.44.0()(64bit)
libboost_regex-mt.so.1.44.0()(64bit)
package: ogre-cg-1.6.1-4.fc12.x86_64 from rpmfusion-nonfree-rawhide
unresolved deps:
libOgreMain-1.6.4.so()(64bit)
package: pdflib-lite-perl-7.0.5-1.fc14.x86_64 from rpmfusion-nonfree-rawhide
unresolved deps:
perl(:MODULE_COMPAT_5.10.1)
package: pdflib-lite-python-7.0.5-1.fc14.x86_64 from
rpmfusion-nonfree-rawhide
unresolved deps:
python(abi) = 0:2.6
11:26 a.m.
Hi all,
On 05/28/2011 08:29 PM, Thorsten Leemhuis wrote:
Hi!
I was a bit rude earlier today and without any warning removed a few
packages from the devel repos (that just became the F15 release repos)
due to broken deps. See the list below for details; would be good if
anybody would tell the maintainers directly, but I don't care about RPM
Fusion enough these days to file bugs myself. Of course all of them can
simply be reintroduced by building a update.
<snip>
= Nonfree =
ec2-api-tools-1.4.2.4-1.fc15.src.rpm
frogatto-1.0.3-2.fc14.src.rpm
I've taken care of frogatto.
Regards,
Hans
1:19 p.m.
Hi,
On 05/30/2011 01:26 PM, Hans de Goede wrote:
Hi all,
On 05/28/2011 08:29 PM, Thorsten Leemhuis wrote:
> Hi!
>
> I was a bit rude earlier today and without any warning removed a few
> packages from the devel repos (that just became the F15 release repos)
> due to broken deps. See the list below for details; would be good if
> anybody would tell the maintainers directly, but I don't care about RPM
> Fusion enough these days to file bugs myself. Of course all of them can
> simply be reintroduced by building a update.
>
<snip>
> = Nonfree =
>
> ec2-api-tools-1.4.2.4-1.fc15.src.rpm
> frogatto-1.0.3-2.fc14.src.rpm
I've taken care of frogatto.
Hmm, this has not gone completely as planned, I set of a build
from devel, which got an fc15 tag rather then an fc16 tag, which
I noticed when I tried to actual do another build from the F-15
branch (which does have the same commits as devel now, but no tag
since that tag now exists on the devel branch).
Note the devel branch still getting an fc15 tag seems to be correct,
since the builder config for devel builds still points to f15 repos.
So we have a proper build for frogatto now, but it should end up
in both the F-15 and devel repo's not just the devel repo ...
Regards,
Hans
4:33 p.m.
Hans de Goede wrote on 30.05.2011 15:19:
On 05/30/2011 01:26 PM, Hans de Goede wrote:
> On 05/28/2011 08:29 PM, Thorsten Leemhuis wrote:
>> I was a bit rude earlier today and without any warning removed a few
>> packages from the devel repos (that just became the F15 release repos)
>> due to broken deps. See the list below for details; would be good if
>> anybody would tell the maintainers directly, but I don't care about RPM
>> Fusion enough these days to file bugs myself. Of course all of them can
>> simply be reintroduced by building a update.
> <snip>
>
>> = Nonfree =
>>
>> ec2-api-tools-1.4.2.4-1.fc15.src.rpm
>> frogatto-1.0.3-2.fc14.src.rpm
>
> I've taken care of frogatto.
Hmm, this has not gone completely as planned, I set of a build
from devel, which got an fc15 tag rather then an fc16 tag, which
I noticed when I tried to actual do another build from the F-15
branch (which does have the same commits as devel now, but no tag
since that tag now exists on the devel branch).
Note the devel branch still getting an fc15 tag seems to be correct,
since the builder config for devel builds still points to f15 repos.
So we have a proper build for frogatto now, but it should end up
in both the F-15 and devel repo's not just the devel repo ...
That will happen.
Btw, Xavier handled all the changes on the Infra side and I assume he'll
update the builder configs to point to F16 over the next few days.
In case someone wonders what I did for the actual branching, here are
the rough steps:
* remove all kmod packages from the devel repos
* build a buildsys-build-rpmfusion package that contained a hard dep on
the F15 release kernel
* rebuild all kmods and make them build akmod packages, too
* check for broken deps and find a "solution" for them
* create a signing key for F16
* add the public key to the rpmfusion-{non,}free-release packages fopr
F13, F14 and F15
* build rpmfusion-{non,}free-release packages for F15 that have the
proper repos enabled and rawhide disabled
* push all of that
* for free and nonfree something like this:
mkdir releases/15/
cp -a development/ releases/15/Everything
* ask adrianr to make changes in the MirrorManager (in fact he asked me
before I asked him)
* build kmods for the updated kernel
CU
knurd
5:49 p.m.
Hi,
On 05/30/2011 06:33 PM, Thorsten Leemhuis wrote:
Hans de Goede wrote on 30.05.2011 15:19:
> On 05/30/2011 01:26 PM, Hans de Goede wrote:
>> On 05/28/2011 08:29 PM, Thorsten Leemhuis wrote:
>>> I was a bit rude earlier today and without any warning removed a few
>>> packages from the devel repos (that just became the F15 release repos)
>>> due to broken deps. See the list below for details; would be good if
>>> anybody would tell the maintainers directly, but I don't care about RPM
>>> Fusion enough these days to file bugs myself. Of course all of them can
>>> simply be reintroduced by building a update.
>> <snip>
>>
>>> = Nonfree =
>>>
>>> ec2-api-tools-1.4.2.4-1.fc15.src.rpm
>>> frogatto-1.0.3-2.fc14.src.rpm
>>
>> I've taken care of frogatto.
>
> Hmm, this has not gone completely as planned, I set of a build
> from devel, which got an fc15 tag rather then an fc16 tag, which
> I noticed when I tried to actual do another build from the F-15
> branch (which does have the same commits as devel now, but no tag
> since that tag now exists on the devel branch).
>
> Note the devel branch still getting an fc15 tag seems to be correct,
> since the builder config for devel builds still points to f15 repos.
>
> So we have a proper build for frogatto now, but it should end up
> in both the F-15 and devel repo's not just the devel repo ...
That will happen.
Thanks, and also many thanks for taking care of the repo branching!
Btw, Xavier handled all the changes on the Infra side and I assume
he'll
update the builder configs to point to F16 over the next few days.
Many thanks to Xavier for his hard work too!
Regards,
Hans
7:38 p.m.
On Mon, May 30, 2011 at 11:33 AM, Thorsten Leemhuis
<fedora(a)leemhuis.info> wrote:
In case someone wonders what I did for the actual branching, here
are
the rough steps:
* remove all kmod packages from the devel repos
* build a buildsys-build-rpmfusion package that contained a hard dep on
the F15 release kernel
* rebuild all kmods and make them build akmod packages, too
* check for broken deps and find a "solution" for them
* create a signing key for F16
* add the public key to the rpmfusion-{non,}free-release packages fopr
F13, F14 and F15
* build rpmfusion-{non,}free-release packages for F15 that have the
proper repos enabled and rawhide disabled
* push all of that
* for free and nonfree something like this:
mkdir releases/15/
cp -a development/ releases/15/Everything
* ask adrianr to make changes in the MirrorManager (in fact he asked me
before I asked him)
* build kmods for the updated kernel
I have created a rough wiki page[1] from this information to be
expounded upon. It will need to be made suitably version generic but I
didn't want this info to get lost.
I'm not sure what the right syntax is for "code" in the RPM Fusion
wiki, <pre>...</pre> didn't work like it does on the Fedora wiki.
Richard
[1] http://rpmfusion.org/Branching
5:50 a.m.
Richard Shaw wrote on 30.05.2011 21:38:
On Mon, May 30, 2011 at 11:33 AM, Thorsten Leemhuis
<fedora(a)leemhuis.info> wrote:
> In case someone wonders what I did for the actual branching, here are
> the rough steps:
>
> * remove all kmod packages from the devel repos
> * build a buildsys-build-rpmfusion package that contained a hard dep on
> the F15 release kernel
> * rebuild all kmods and make them build akmod packages, too
> * check for broken deps and find a "solution" for them
> * create a signing key for F16
> * add the public key to the rpmfusion-{non,}free-release packages fopr
> F13, F14 and F15
> * build rpmfusion-{non,}free-release packages for F15 that have the
> proper repos enabled and rawhide disabled
> * push all of that
> * for free and nonfree something like this:
> mkdir releases/15/
> cp -a development/ releases/15/Everything
Actually it's
cp -al development/ releases/15/Everything
(Makes life for mirrors a whole lot easier)
> * ask adrianr to make changes in the MirrorManager (in fact he
asked me
> before I asked him)
> * build kmods for the updated kernel
And resigning the devel repo with the F16 key over the next few days:
I have created a rough wiki page[1] from this information to be
expounded upon. It will need to be made suitably version generic but I
didn't want this info to get lost.
I'm not sure what the right syntax is for "code" in the RPM Fusion
wiki, <pre>...</pre> didn't work like it does on the Fedora wiki.
Richard
[1] http://rpmfusion.org/Branching
You might want to merge it into
http://www.rpmfusion.org/Infrastructure/PrepareRelease
CU
knurd
8:05 a.m.
On 05/30/2011 08:38 PM, Richard Shaw wrote:
On Mon, May 30, 2011 at 11:33 AM, Thorsten Leemhuis
<fedora(a)leemhuis.info> wrote:
> In case someone wonders what I did for the actual branching, here are
> the rough steps:
>
> * remove all kmod packages from the devel repos
> * build a buildsys-build-rpmfusion package that contained a hard dep on
> the F15 release kernel
> * rebuild all kmods and make them build akmod packages, too
> * check for broken deps and find a "solution" for them
> * create a signing key for F16
> * add the public key to the rpmfusion-{non,}free-release packages fopr
> F13, F14 and F15
> * build rpmfusion-{non,}free-release packages for F15 that have the
> proper repos enabled and rawhide disabled
> * push all of that
> * for free and nonfree something like this:
> mkdir releases/15/
> cp -a development/ releases/15/Everything
> * ask adrianr to make changes in the MirrorManager (in fact he asked me
> before I asked him)
> * build kmods for the updated kernel
I have created a rough wiki page[1] from this information to be
expounded upon. It will need to be made suitably version generic but I
didn't want this info to get lost.
I'm not sure what the right syntax is for "code" in the RPM Fusion
wiki,<pre>...</pre> didn't work like it does on the Fedora wiki.
It's a moin wiki; Fedora switched from moin to mediawiki quite some time
ago.
You can find a bunch of help pages here:
http://www.rpmfusion.org/HelpOnEditing
Paul.
2:25 p.m.
On Tue, May 31, 2011 at 3:05 AM, Paul Howarth <paul(a)city-fan.org> wrote:
It's a moin wiki; Fedora switched from moin to mediawiki quite
some time
ago.
You can find a bunch of help pages here:
http://www.rpmfusion.org/HelpOnEditing
I tried the triple curly brackets but it didn't seem to work... Of
course the strikethough isn't working for me either... Maybe we should
switch? :)
Richard
2:45 p.m.
On 05/31/2011 03:25 PM, Richard Shaw wrote:
On Tue, May 31, 2011 at 3:05 AM, Paul
Howarth<paul(a)city-fan.org> wrote:
> It's a moin wiki; Fedora switched from moin to mediawiki quite some time
> ago.
>
> You can find a bunch of help pages here:
> http://www.rpmfusion.org/HelpOnEditing
I tried the triple curly brackets but it didn't seem to work... Of
course the strikethough isn't working for me either... Maybe we should
switch? :)
Curly brackets seem to work OK for me.
Paul.
5:48 a.m.
Thorsten Leemhuis wrote on 30.05.2011 18:33:
Hans de Goede wrote on 30.05.2011 15:19:
> On 05/30/2011 01:26 PM, Hans de Goede wrote:
>> On 05/28/2011 08:29 PM, Thorsten Leemhuis wrote:
That will happen.
Btw, Xavier handled all the changes on the Infra side and I assume he'll
update the builder configs to point to F16 over the next few days.
Sorry, I was unprecise here. I should have written "I assume that will
happen; Xavier handled all the changes on the Infra side and I assume
he'll handle this over the next few days, too".
CU
knurd
4714
days inactive
4717
days old
rpmfusion-developers@lists.rpmfusion.org
10 comments
4 participants
participants (4)
-
Hans de Goede -
Paul Howarth -
Richard Shaw -
Thorsten Leemhuis