Re: [Mageia-dev] bumblebee in mageia (and mentoring)
Luca Olivetti wrote: > Al 15/04/12 07:08, En/na simple w8 ha escrit: > >>> I have revised the specs and here they are attached. >>> >>> Is anyone available that could help me in the mentoring proccess? >> >> Well seams that last bumblebee spec missed the scriplets to handle >> systemd services. > > I've been given a laptop with optimus technology. > I took the following SRPMS and rebuilt them for mageia 2: > > bumblebee-3.0-11.mga3.src.rpm > dkms-acpi_call-0.1-2.mga3.src.rpm > dkms-bbswitch-0.4.2-1.mga3.src.rpm > libbsd-0.4.1-1.mga3.src.rpm > virtualgl-2.3.1-1.mga3.src.rpm > > > I have two issues (just FYI): Hi Luca, I don't know if simple w8 is with us still, I haven't seen him active in a while. Would you be interested in getting more directly involved, such that you could fix any issues yourself? If so, see the information on the Mageia Wiki about packaging mentoring, and come see us on IRC.
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
Al 15/04/12 07:08, En/na simple w8 ha escrit: >> I have revised the specs and here they are attached. >> >> Is anyone available that could help me in the mentoring proccess? > > Well seams that last bumblebee spec missed the scriplets to handle > systemd services. I've been given a laptop with optimus technology. I took the following SRPMS and rebuilt them for mageia 2: bumblebee-3.0-11.mga3.src.rpm dkms-acpi_call-0.1-2.mga3.src.rpm dkms-bbswitch-0.4.2-1.mga3.src.rpm libbsd-0.4.1-1.mga3.src.rpm virtualgl-2.3.1-1.mga3.src.rpm I have two issues (just FYI): 1) the [driver-nvidia] section in the configuration file should have a line KernelDriver=nvidia-current otherwise bumbleebed couldn't load the module and wouldn't start 2) running glxspheres with optirun, not only takes 5 seconds to start, but is slower than with the integrated graphics card (60 frames/sec. without optirun vs. 40 frames/sec. with optirun). I see they mention it in the FAQ, so this isn't probably an issue with the packages. I'm using the 310.32 nvidia driver built with the script by Anssi Hannula http://onse.fi/nvidia-mgabuild/ Bye -- Luca
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/14 simple w8 : > 2012/4/10 simple w8 : >> 2012/4/10 Guillaume Rousse : >>> Le 10/04/2012 22:15, simple w8 a écrit : >>> For what i have discussed with rpm and rpm5 developers, if you use a plain require its enough, so adding the same require for scripts is simply unnecessary, and im just relying on what rpm devepers said, now if Mageia has a policy that ignores that its different. >>> >>> I'd rather say we're not aware of such change. If you can point us to such a >>> discussion, it could be a good occasion to revise our habits :) >>> >>> -- >>> BOFH excuse #354: >>> >>> Chewing gum on /dev/sd3c >> >> Well that was discussed in irc, so i cant point any URL, but that can >> be easily checked if asking any of the current developers that hang at >> #rpm.org and/or #rpm > > I have revised the specs and here they are attached. > > Is anyone available that could help me in the mentoring proccess? Well seams that last bumblebee spec missed the scriplets to handle systemd services. bumblebee.spec Description: Binary data
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/10 simple w8 : > 2012/4/10 Guillaume Rousse : >> Le 10/04/2012 22:15, simple w8 a écrit : >> >>> For what i have discussed with rpm and rpm5 developers, if you use a >>> plain require its enough, so adding the same require for scripts is >>> simply unnecessary, and im just relying on what rpm devepers said, now >>> if Mageia has a policy that ignores that its different. >> >> I'd rather say we're not aware of such change. If you can point us to such a >> discussion, it could be a good occasion to revise our habits :) >> >> -- >> BOFH excuse #354: >> >> Chewing gum on /dev/sd3c > > Well that was discussed in irc, so i cant point any URL, but that can > be easily checked if asking any of the current developers that hang at > #rpm.org and/or #rpm I have revised the specs and here they are attached. Is anyone available that could help me in the mentoring proccess? bamf.spec Description: Binary data indicator-application.spec Description: Binary data virtualgl.spec Description: Binary data indicator-appmenu.spec Description: Binary data libappindicator.spec Description: Binary data libindicator.spec Description: Binary data bumblebee-ui.spec Description: Binary data dkms-acpi_call.spec Description: Binary data bumblebee.spec Description: Binary data dkms-bbswitch.spec Description: Binary data optidesk.spec Description: Binary data libbsd.spec Description: Binary data
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/10 Guillaume Rousse : > Le 10/04/2012 22:15, simple w8 a écrit : > >> For what i have discussed with rpm and rpm5 developers, if you use a >> plain require its enough, so adding the same require for scripts is >> simply unnecessary, and im just relying on what rpm devepers said, now >> if Mageia has a policy that ignores that its different. > > I'd rather say we're not aware of such change. If you can point us to such a > discussion, it could be a good occasion to revise our habits :) > > -- > BOFH excuse #354: > > Chewing gum on /dev/sd3c Well that was discussed in irc, so i cant point any URL, but that can be easily checked if asking any of the current developers that hang at #rpm.org and/or #rpm
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
Le 10/04/2012 22:15, simple w8 a écrit : For what i have discussed with rpm and rpm5 developers, if you use a plain require its enough, so adding the same require for scripts is simply unnecessary, and im just relying on what rpm devepers said, now if Mageia has a policy that ignores that its different. I'd rather say we're not aware of such change. If you can point us to such a discussion, it could be a good occasion to revise our habits :) -- BOFH excuse #354: Chewing gum on /dev/sd3c
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/10 Pascal Terjan :
> On Tue, Apr 10, 2012 at 20:45, simple w8 wrote:
>> 2012/4/10 Pascal Terjan :
>>> On Tue, Apr 10, 2012 at 19:35, simple w8 wrote:
>> %install
>> make install DESTDIR=%{buildroot} \
>
> %makeinstall_std
Here you really need to spefify them, with %makeinstall_std fails
>>>
>>> %makeinstall then ?
>>
>> It also fails, i did tried both macros.
>>
>> libdir=%{_libdir} \
>> usrlibdir=%{_libdir} \
>> exec_prefix=%{_prefix}
>>
> [...]
>> optidesk.spec
>>
>>
>> Name: optidesk
>> Summary: Tool to configure .desktop files to run with optirun
>> Group: Graphical desktop/Other
>> Version: 0.1
>> Release: 1
>> URL: https://github.com/Bumblebee-Project/optidesk
>> License: GPLv3
>> # source from git repo git://github.com/Bumblebee-Project/optidesk.git
>> Source0: %{name}.tar.xz
>
> Tarball needs to be versioned.
I did add a comment saying its from git, but i usually use to create a
macro and put some like this:
Source0: %{?git:%{name}}%{!?git:%{name}-%{version}}.tar.xz
but still there isnt any version released
>>>
>>> Yes but you should add one, like the date of the snapshot, or the
>>> hash. Else different tarball from git will have the same name.
>>
>> Yes it does make sense.
>>
>> BuildArch: noarch
>> Requires(post): dkms
>> Requires(preun):dkms
>
> Needs to require dkms.
AFAIK dkms its only used in post and preun scriptlets., so why add
another plain require?
>>>
>>> Because you need to have it on the system to get this module rebuilt
>>> when you install a new kernel, not only when you install this package
>>
>> If we add a plain require theres no need to have requires in
>> scriplets, at least more recently that was clarified, a plain require
>> is enough.
>
> It is needed to have it for ordering in the same transaction
> Requires only guarantees that dkms will be there at the end of the rpm
> transaction installing this package, but it may be installed after
> this package if they are in the same transaction. Adding
> requires(post) makes rpm install dkms before this one if they are in
> the same transaction.
For what i have discussed with rpm and rpm5 developers, if you use a
plain require its enough, so adding the same require for scripts is
simply unnecessary, and im just relying on what rpm devepers said, now
if Mageia has a policy that ignores that its different.
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
Op dinsdag 10 april 2012 21:53:57 schreef Guillaume Rousse: > Le 10/04/2012 21:12, Maarten Vanraes a écrit : > if [ $1 -eq 1 ]; then > > # Initial set > # Enable (but don't start) the unit by default > /bin/systemctl enable bumblebeed.service > > fi > >>> > >>> I don't think this stuff is needed on Mageia, that is done by default. > >> > >> Really? I didnt knew about it, is there any page documenting that? > >> Im quite curious about how is done :) > > just read the the add-service helper code, or alternatively the > rpm-helper README file. > > > perhaps filetriggers or the post and preun service helpers do all this > > automagically... i don't know, i usually just look at other packages. > > > > i think a provided existing service file is picked up by filetriggers > > No, that's handled by add-service helper here. thanks for correcting me
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
Op dinsdag 10 april 2012 21:28:19 schreef simple w8: [...] > > better to follow the policy. > > I dont know about mageia policies, but i will read about them so i can > start using them from now on. check https://wiki.mageia.org/en/Policies , you don't have to read all of them, but it's nice to look at what kind of policies exist, so that later you can look them up if required. [...] > > you can afterwards make a kmod-bbswitch and kmod-acpi_call packages that > > make prebuilt modules for all available kernels. > > Yeap, i have seen those kind of packages and that way theres no need > to use a dkms. well, except to actually build the kmod package, since it requires the dkms package :-) [...] > > perhaps filetriggers or the post and preun service helpers do all this > > automagically... i don't know, i usually just look at other packages. > > > > i think a provided existing service file is picked up by filetriggers > > I do see one systemd filetrigger: systemd-daemon-reload.script > > but i would like to know hows processed, so far for what i have seen i > dont see how that is possible, to put systemd running services without > put them in the scripts. > > And to remember that bumblebee is provided with service files for > systemd and sysvinit, i did had that caution, thats why i put in > scripts both usage. > > Still i think it would be better to simply keep the ones for systemd, > since its the one used by default. well, if i was you, comment out the code and see if it actually does enable it by default. i'm definately not an expert, but for mariadb i didn't have to enable it, it worked like that... since i have not seen any other packages where it effectively does that, i don't think it's required. [...] > > iinm you can also add extra option to %cmake. if it's possible it'd be > > nice to have %cmake in it. if there would be systemwide changes at a > > later time, possibly due to changed newer cmake behavior, or whatever, > > it can be picked up without much effort. > > > > also it looks better to me, having all cmake packages using %cmake :-) > > Did you read what i wrote? ? of course i did, why else would i take the effort to reply? > i did tried to use %cmake but build fails, so its really need to use > it explicitely like its currently, and the same goes for when i did > not used %makeinstall_std in libbsd. well as you already know, %cmake evaluates to cmake with some extra stuff, so if one of these things give you difficulty, either it points to a point that can be improved, or you can just override them for the ones you need. that way, you can still make it work with %cmake. [...]
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
Le 10/04/2012 21:12, Maarten Vanraes a écrit : if [ $1 -eq 1 ]; then # Initial set # Enable (but don't start) the unit by default /bin/systemctl enable bumblebeed.service fi I don't think this stuff is needed on Mageia, that is done by default. Really? I didnt knew about it, is there any page documenting that? Im quite curious about how is done :) just read the the add-service helper code, or alternatively the rpm-helper README file. perhaps filetriggers or the post and preun service helpers do all this automagically... i don't know, i usually just look at other packages. i think a provided existing service file is picked up by filetriggers No, that's handled by add-service helper here. -- Any program will expand to fill available memory. -- Murphy's Laws of Computer Programming n°11
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
On Tue, Apr 10, 2012 at 20:45, simple w8 wrote:
> 2012/4/10 Pascal Terjan :
>> On Tue, Apr 10, 2012 at 19:35, simple w8 wrote:
> %install
> make install DESTDIR=%{buildroot} \
%makeinstall_std
>>>
>>> Here you really need to spefify them, with %makeinstall_std fails
>>
>> %makeinstall then ?
>
> It also fails, i did tried both macros.
>
> libdir=%{_libdir} \
> usrlibdir=%{_libdir} \
> exec_prefix=%{_prefix}
>
[...]
> optidesk.spec
>
>
> Name: optidesk
> Summary: Tool to configure .desktop files to run with optirun
> Group: Graphical desktop/Other
> Version: 0.1
> Release: 1
> URL: https://github.com/Bumblebee-Project/optidesk
> License: GPLv3
> # source from git repo git://github.com/Bumblebee-Project/optidesk.git
> Source0: %{name}.tar.xz
Tarball needs to be versioned.
>>>
>>> I did add a comment saying its from git, but i usually use to create a
>>> macro and put some like this:
>>>
>>> Source0: %{?git:%{name}}%{!?git:%{name}-%{version}}.tar.xz
>>>
>>> but still there isnt any version released
>>
>> Yes but you should add one, like the date of the snapshot, or the
>> hash. Else different tarball from git will have the same name.
>
> Yes it does make sense.
>
> BuildArch: noarch
> Requires(post): dkms
> Requires(preun):dkms
Needs to require dkms.
>>>
>>> AFAIK dkms its only used in post and preun scriptlets., so why add
>>> another plain require?
>>
>> Because you need to have it on the system to get this module rebuilt
>> when you install a new kernel, not only when you install this package
>
> If we add a plain require theres no need to have requires in
> scriplets, at least more recently that was clarified, a plain require
> is enough.
It is needed to have it for ordering in the same transaction
Requires only guarantees that dkms will be there at the end of the rpm
transaction installing this package, but it may be installed after
this package if they are in the same transaction. Adding
requires(post) makes rpm install dkms before this one if they are in
the same transaction.
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
Le 10/04/2012 21:45, simple w8 a écrit : Because you need to have it on the system to get this module rebuilt when you install a new kernel, not only when you install this package If we add a plain require theres no need to have requires in scriplets, at least more recently that was clarified, a plain require is enough. A dependency only ensure your package and the depended one will get installed in the same transaction, but in any order. Which often translates into: - dkms-stuff - dmks In this case, %post of dkms-stuff run before dkms get installed, and fails. -- Why are they called 'stands' when they're made for sitting? -- Why Why Why n°24
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/10 Pascal Terjan :
> On Tue, Apr 10, 2012 at 19:35, simple w8 wrote:
%install
make install DESTDIR=%{buildroot} \
>>>
>>> %makeinstall_std
>>
>> Here you really need to spefify them, with %makeinstall_std fails
>
> %makeinstall then ?
It also fails, i did tried both macros.
libdir=%{_libdir} \
usrlibdir=%{_libdir} \
exec_prefix=%{_prefix}
>>> [...]
optidesk.spec
Name: optidesk
Summary: Tool to configure .desktop files to run with optirun
Group: Graphical desktop/Other
Version: 0.1
Release: 1
URL: https://github.com/Bumblebee-Project/optidesk
License: GPLv3
# source from git repo git://github.com/Bumblebee-Project/optidesk.git
Source0: %{name}.tar.xz
>>>
>>> Tarball needs to be versioned.
>>
>> I did add a comment saying its from git, but i usually use to create a
>> macro and put some like this:
>>
>> Source0: %{?git:%{name}}%{!?git:%{name}-%{version}}.tar.xz
>>
>> but still there isnt any version released
>
> Yes but you should add one, like the date of the snapshot, or the
> hash. Else different tarball from git will have the same name.
Yes it does make sense.
BuildArch: noarch
Requires(post): dkms
Requires(preun):dkms
>>>
>>> Needs to require dkms.
>>
>> AFAIK dkms its only used in post and preun scriptlets., so why add
>> another plain require?
>
> Because you need to have it on the system to get this module rebuilt
> when you install a new kernel, not only when you install this package
If we add a plain require theres no need to have requires in
scriplets, at least more recently that was clarified, a plain require
is enough.
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
On Tue, Apr 10, 2012 at 19:35, simple w8 wrote:
>>> %install
>>> make install DESTDIR=%{buildroot} \
>>
>> %makeinstall_std
>
> Here you really need to spefify them, with %makeinstall_std fails
%makeinstall then ?
>>> libdir=%{_libdir} \
>>> usrlibdir=%{_libdir} \
>>> exec_prefix=%{_prefix}
>>>
>> [...]
>>> optidesk.spec
>>>
>>>
>>> Name: optidesk
>>> Summary: Tool to configure .desktop files to run with optirun
>>> Group: Graphical desktop/Other
>>> Version: 0.1
>>> Release: 1
>>> URL: https://github.com/Bumblebee-Project/optidesk
>>> License: GPLv3
>>> # source from git repo git://github.com/Bumblebee-Project/optidesk.git
>>> Source0: %{name}.tar.xz
>>
>> Tarball needs to be versioned.
>
> I did add a comment saying its from git, but i usually use to create a
> macro and put some like this:
>
> Source0: %{?git:%{name}}%{!?git:%{name}-%{version}}.tar.xz
>
> but still there isnt any version released
Yes but you should add one, like the date of the snapshot, or the
hash. Else different tarball from git will have the same name.
>>> BuildArch: noarch
>>> Requires(post): dkms
>>> Requires(preun):dkms
>>
>> Needs to require dkms.
>
> AFAIK dkms its only used in post and preun scriptlets., so why add
> another plain require?
Because you need to have it on the system to get this module rebuilt
when you install a new kernel, not only when you install this package
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/10 Maarten Vanraes :
> i have some sparsely extra comments, i hope i'm correct on this...
>
>
> Op dinsdag 10 april 2012 20:35:26 schreef simple w8:
>> 2012/4/10 Anssi Hannula :
>> > 10.04.2012 07:46, simple w8 kirjoitti:
>> >> Currently i dont have any account to be able to comit these new
>> >> packages for the distro so i ask if someone can review the specs so
>> >> that these packages can start existing in the distro, and i also ask
>> >> if theres someone that can help me with mentoring
>> >
>> > Reviewed below. However, there looks to be quite a lot of work
>> > remaining, so I don't think I'll be able to help you personally with the
>> > issues. I hope you'll find a mentor who'll help you through.
>> >
>> >> Name: libbsd
>> >> Summary: Library providing BSD-compatible functions for portability
>> >>
>> >>[...]
>> >>
>> >> %{_libdir}/libbsd.so.%{major}*
>> >
>> > [...]
>> >
>> >> %{_libdir}/libbsd.so
>> >
>> > [...]
>> >
>> > We already have libbsd.a from glibc-devel, which would conflict with
>> > this. If they are really different libraries, something drastic would
>> > have to be done (e.g. renaming or dropping one). I suspect they are the
>> > same, though, in which case this isn't needed.
>> >
>> >> %prep
>> >> %setup -q
>> >> # fix encoding of flopen.3 man page
>> >> for f in src/flopen.3; do
>> >> iconv -f iso8859-1 -t utf-8 $f >$f.conv
>> >> touch -r $f $f.conv
>> >> mv $f.conv $f
>> >> done
>> >>
>> >> %build
>> >> %make
>> >
>> > %optflags not used.
>> >
>> >> %install
>> >> make install DESTDIR=%{buildroot} \
>> >
>> > %makeinstall_std
>>
>> Here you really need to spefify them, with %makeinstall_std fails
>>
>> >> libdir=%{_libdir} \
>> >> usrlibdir=%{_libdir} \
>> >> exec_prefix=%{_prefix}
>> >
>> > [...]
>> >
>> >> optidesk.spec
>> >>
>> >>
>> >> Name: optidesk
>> >> Summary: Tool to configure .desktop files to run with optirun
>> >> Group: Graphical desktop/Other
>> >> Version: 0.1
>> >> Release: 1
>> >> URL: https://github.com/Bumblebee-Project/optidesk
>> >> License: GPLv3
>> >> # source from git repo git://github.com/Bumblebee-Project/optidesk.git
>> >> Source0: %{name}.tar.xz
>> >
>> > Tarball needs to be versioned.
>>
>> I did add a comment saying its from git, but i usually use to create a
>> macro and put some like this:
>>
>> Source0: %{?git:%{name}}%{!?git:%{name}-%{version}}.tar.xz
>>
>> but still there isnt any version released
>>
>> >> Requires: bumblebee
>> >>
>> >> %description
>> >> This tool is intended to be an easy way of configuring your desired
>> >> applications to be run through Bumblebee. It will allow to create
>> >> and modify a menu entry with an alternative (Optirun) version of the
>> >> default launcher.
>> >>
>> >> %files
>> >> %{_bindir}/%{name}
>> >>
>> >>
>> >> %prep
>> >> %setup -qn %{name}
>> >>
>> >> %build
>> >> autoreconf -fi
>> >> %configure
>> >
>> > %configure2_5x
>>
>> I also use to use configure2_5X~but here would not make any
>> difference, but yes here i didnt put because i missed ateention on
>> this line
>>
>> >> %make
>> >
>> > [...]
>> >
>> >> %changelog
>> >> * Mon Mar 19 2012 Simple 3.0-1
>> >> - initial package
>> >
>> > No single-entry changelog needed for imported packages, it will be
>> > created from the import commit message. (applies to all .specs)
>>
>> Even so i do add an entry in changelog for my personall reports.
>>
>> >> dkms-bbswitch.spec
>> >>
>> >>
>> >> %define oname bbswitch
>> >>
>> >> Name: dkms-%{oname}
>> >> Summary: bbswitch - Optimus GPU power switcher
>> >> Group: System/Kernel and hardware
>> >> Version: 0.4.1
>> >> Release: %mkrel 1
>> >> License: GPLv3
>> >> URL: https://github.com/Bumblebee-Project/bbswitch
>> >> # source from git repo git://github.com/Bumblebee-Project/bbswitch.git
>> >> Source0: %{oname}.tar.xz
>> >
>> > Tarball needs to be versioned.
>>
>> This is from git and already explained that there was no release
>
> i like to add that if it's a git version, it's best if to have some kind of
> git version on it. so it can be uniquely named. same git version should also
> be used in the version or release.
>
>> >> BuildArch: noarch
>> >> Requires(post): dkms
>> >> Requires(preun):dkms
>> >
>> > Needs to require dkms.
>>
>> AFAIK dkms its only used in post and preun scriptlets., so why add
>> another plain require?
>
> it's in the policy, if you think the policy is incorrect, you should send a
> separate email about it.
>
> better to follow the policy.
I dont know about mageia policies, but i will read about them so i can
start using them from now on.
>> >> %description
>> >> bbswitch is a kernel module which automatically detects the required
>> >> ACPI calls for two kinds of Optimus laptops. It has been verified to
>> >> work with "real" Optimus and "legacy" Optimus laptops (at least, that
>> >> is how I call them
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
i have some sparsely extra comments, i hope i'm correct on this...
Op dinsdag 10 april 2012 20:35:26 schreef simple w8:
> 2012/4/10 Anssi Hannula :
> > 10.04.2012 07:46, simple w8 kirjoitti:
> >> Currently i dont have any account to be able to comit these new
> >> packages for the distro so i ask if someone can review the specs so
> >> that these packages can start existing in the distro, and i also ask
> >> if theres someone that can help me with mentoring
> >
> > Reviewed below. However, there looks to be quite a lot of work
> > remaining, so I don't think I'll be able to help you personally with the
> > issues. I hope you'll find a mentor who'll help you through.
> >
> >> Name: libbsd
> >> Summary: Library providing BSD-compatible functions for portability
> >>
> >>[...]
> >>
> >> %{_libdir}/libbsd.so.%{major}*
> >
> > [...]
> >
> >> %{_libdir}/libbsd.so
> >
> > [...]
> >
> > We already have libbsd.a from glibc-devel, which would conflict with
> > this. If they are really different libraries, something drastic would
> > have to be done (e.g. renaming or dropping one). I suspect they are the
> > same, though, in which case this isn't needed.
> >
> >> %prep
> >> %setup -q
> >> # fix encoding of flopen.3 man page
> >> for f in src/flopen.3; do
> >> iconv -f iso8859-1 -t utf-8 $f >$f.conv
> >> touch -r $f $f.conv
> >> mv $f.conv $f
> >> done
> >>
> >> %build
> >> %make
> >
> > %optflags not used.
> >
> >> %install
> >> make install DESTDIR=%{buildroot} \
> >
> > %makeinstall_std
>
> Here you really need to spefify them, with %makeinstall_std fails
>
> >> libdir=%{_libdir} \
> >> usrlibdir=%{_libdir} \
> >> exec_prefix=%{_prefix}
> >
> > [...]
> >
> >> optidesk.spec
> >>
> >>
> >> Name: optidesk
> >> Summary:Tool to configure .desktop files to run with optirun
> >> Group: Graphical desktop/Other
> >> Version:0.1
> >> Release:1
> >> URL:https://github.com/Bumblebee-Project/optidesk
> >> License:GPLv3
> >> # source from git repo git://github.com/Bumblebee-Project/optidesk.git
> >> Source0: %{name}.tar.xz
> >
> > Tarball needs to be versioned.
>
> I did add a comment saying its from git, but i usually use to create a
> macro and put some like this:
>
> Source0: %{?git:%{name}}%{!?git:%{name}-%{version}}.tar.xz
>
> but still there isnt any version released
>
> >> Requires: bumblebee
> >>
> >> %description
> >> This tool is intended to be an easy way of configuring your desired
> >> applications to be run through Bumblebee. It will allow to create
> >> and modify a menu entry with an alternative (Optirun) version of the
> >> default launcher.
> >>
> >> %files
> >> %{_bindir}/%{name}
> >>
> >>
> >> %prep
> >> %setup -qn %{name}
> >>
> >> %build
> >> autoreconf -fi
> >> %configure
> >
> > %configure2_5x
>
> I also use to use configure2_5X~but here would not make any
> difference, but yes here i didnt put because i missed ateention on
> this line
>
> >> %make
> >
> > [...]
> >
> >> %changelog
> >> * Mon Mar 19 2012 Simple 3.0-1
> >> - initial package
> >
> > No single-entry changelog needed for imported packages, it will be
> > created from the import commit message. (applies to all .specs)
>
> Even so i do add an entry in changelog for my personall reports.
>
> >> dkms-bbswitch.spec
> >>
> >>
> >> %define oname bbswitch
> >>
> >> Name: dkms-%{oname}
> >> Summary:bbswitch - Optimus GPU power switcher
> >> Group: System/Kernel and hardware
> >> Version:0.4.1
> >> Release:%mkrel 1
> >> License:GPLv3
> >> URL:https://github.com/Bumblebee-Project/bbswitch
> >> # source from git repo git://github.com/Bumblebee-Project/bbswitch.git
> >> Source0:%{oname}.tar.xz
> >
> > Tarball needs to be versioned.
>
> This is from git and already explained that there was no release
i like to add that if it's a git version, it's best if to have some kind of
git version on it. so it can be uniquely named. same git version should also
be used in the version or release.
> >> BuildArch:noarch
> >> Requires(post): dkms
> >> Requires(preun):dkms
> >
> > Needs to require dkms.
>
> AFAIK dkms its only used in post and preun scriptlets., so why add
> another plain require?
it's in the policy, if you think the policy is incorrect, you should send a
separate email about it.
better to follow the policy.
> >> %description
> >> bbswitch is a kernel module which automatically detects the required
> >> ACPI calls for two kinds of Optimus laptops. It has been verified to
> >> work with "real" Optimus and "legacy" Optimus laptops (at least, that
> >> is how I call them).
> >>
> >> %files
> >> %{_usrsrc}/%{oname}-%{version}/*
> >>
> >> %post
> >> set -x
> >> dkms add -m %{oname} -v %{version} --rpm_safe_upgrade || :
> >> dkms build -m %{oname} -v %{version} --rpm_safe_upgrade || :
> >> dkms install -m %{oname} -v %{v
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/10 simple w8 :
> 2012/4/10 Anssi Hannula :
>> 10.04.2012 07:46, simple w8 kirjoitti:
>>> Currently i dont have any account to be able to comit these new
>>> packages for the distro so i ask if someone can review the specs so
>>> that these packages can start existing in the distro, and i also ask
>>> if theres someone that can help me with mentoring
>>
>> Reviewed below. However, there looks to be quite a lot of work
>> remaining, so I don't think I'll be able to help you personally with the
>> issues. I hope you'll find a mentor who'll help you through.
>>
>>
>>> Name: libbsd
>>> Summary: Library providing BSD-compatible functions for portability
>>>[...]
>>> %{_libdir}/libbsd.so.%{major}*
>> [...]
>>> %{_libdir}/libbsd.so
>> [...]
>>
>> We already have libbsd.a from glibc-devel, which would conflict with
>> this. If they are really different libraries, something drastic would
>> have to be done (e.g. renaming or dropping one). I suspect they are the
>> same, though, in which case this isn't needed.
>>
>>> %prep
>>> %setup -q
>>> # fix encoding of flopen.3 man page
>>> for f in src/flopen.3; do
>>> iconv -f iso8859-1 -t utf-8 $f >$f.conv
>>> touch -r $f $f.conv
>>> mv $f.conv $f
>>> done
>>>
>>> %build
>>> %make
>>
>> %optflags not used.
>>
>>> %install
>>> make install DESTDIR=%{buildroot} \
>>
>> %makeinstall_std
>
> Here you really need to spefify them, with %makeinstall_std fails
>
>>> libdir=%{_libdir} \
>>> usrlibdir=%{_libdir} \
>>> exec_prefix=%{_prefix}
>>>
>> [...]
>>> optidesk.spec
>>>
>>>
>>> Name: optidesk
>>> Summary: Tool to configure .desktop files to run with optirun
>>> Group: Graphical desktop/Other
>>> Version: 0.1
>>> Release: 1
>>> URL: https://github.com/Bumblebee-Project/optidesk
>>> License: GPLv3
>>> # source from git repo git://github.com/Bumblebee-Project/optidesk.git
>>> Source0: %{name}.tar.xz
>>
>> Tarball needs to be versioned.
>
> I did add a comment saying its from git, but i usually use to create a
> macro and put some like this:
>
> Source0: %{?git:%{name}}%{!?git:%{name}-%{version}}.tar.xz
>
> but still there isnt any version released
>
>
>>> Requires: bumblebee
>>>
>>> %description
>>> This tool is intended to be an easy way of configuring your desired
>>> applications to be run through Bumblebee. It will allow to create
>>> and modify a menu entry with an alternative (Optirun) version of the
>>> default launcher.
>>>
>>> %files
>>> %{_bindir}/%{name}
>>>
>>>
>>> %prep
>>> %setup -qn %{name}
>>>
>>> %build
>>> autoreconf -fi
>>> %configure
>>
>> %configure2_5x
>
> I also use to use configure2_5X~but here would not make any
> difference, but yes here i didnt put because i missed ateention on
> this line
>
>>> %make
>> [...]
>>> %changelog
>>> * Mon Mar 19 2012 Simple 3.0-1
>>> - initial package
>>
>> No single-entry changelog needed for imported packages, it will be
>> created from the import commit message. (applies to all .specs)
>
> Even so i do add an entry in changelog for my personall reports.
>
>>>
>>> dkms-bbswitch.spec
>>>
>>>
>>> %define oname bbswitch
>>>
>>> Name: dkms-%{oname}
>>> Summary: bbswitch - Optimus GPU power switcher
>>> Group: System/Kernel and hardware
>>> Version: 0.4.1
>>> Release: %mkrel 1
>>> License: GPLv3
>>> URL: https://github.com/Bumblebee-Project/bbswitch
>>> # source from git repo git://github.com/Bumblebee-Project/bbswitch.git
>>> Source0: %{oname}.tar.xz
>>
>> Tarball needs to be versioned.
>
> This is from git and already explained that there was no release
>
>>> BuildArch: noarch
>>> Requires(post): dkms
>>> Requires(preun):dkms
>>
>> Needs to require dkms.
>
> AFAIK dkms its only used in post and preun scriptlets., so why add
> another plain require?
>
>>>
>>> %description
>>> bbswitch is a kernel module which automatically detects the required
>>> ACPI calls for two kinds of Optimus laptops. It has been verified to
>>> work with "real" Optimus and "legacy" Optimus laptops (at least, that
>>> is how I call them).
>>>
>>> %files
>>> %{_usrsrc}/%{oname}-%{version}/*
>>>
>>> %post
>>> set -x
>>> dkms add -m %{oname} -v %{version} --rpm_safe_upgrade || :
>>> dkms build -m %{oname} -v %{version} --rpm_safe_upgrade || :
>>> dkms install -m %{oname} -v %{version} --rpm_safe_upgrade || :
>>> /sbin/modprobe %{oname} || :
>>>
>>> %preun
>>> dkms remove --binary -m %{oname} -v %{version} --rpm_safe_upgrade --all || :
>>> /sbin/rmmod %{oname} || :
>>>
>>
>> These scripts are a bit incorrect, see
>> https://wiki.mageia.org/en/DKMS_packaging_policy
>> (some || : should be replaced with &&)
>
> Well i dont think its incorrect, bow if mageia prefers to use another
> code its a different issue.
>
>>> %prep
>>> %setup -qn %{oname}
>>> sed -i 's/#MODULE_VERSION#/%{version}/g' dkms/dkms.conf
>>>
>>> %install
>>> rm -rf %{buildroot}
>>> mkdir -p %{buildroot}%{_usrsrc
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/10 Anssi Hannula :
> 10.04.2012 07:46, simple w8 kirjoitti:
>> Currently i dont have any account to be able to comit these new
>> packages for the distro so i ask if someone can review the specs so
>> that these packages can start existing in the distro, and i also ask
>> if theres someone that can help me with mentoring
>
> Reviewed below. However, there looks to be quite a lot of work
> remaining, so I don't think I'll be able to help you personally with the
> issues. I hope you'll find a mentor who'll help you through.
>
>
>> Name: libbsd
>> Summary: Library providing BSD-compatible functions for portability
>>[...]
>> %{_libdir}/libbsd.so.%{major}*
> [...]
>> %{_libdir}/libbsd.so
> [...]
>
> We already have libbsd.a from glibc-devel, which would conflict with
> this. If they are really different libraries, something drastic would
> have to be done (e.g. renaming or dropping one). I suspect they are the
> same, though, in which case this isn't needed.
>
>> %prep
>> %setup -q
>> # fix encoding of flopen.3 man page
>> for f in src/flopen.3; do
>> iconv -f iso8859-1 -t utf-8 $f >$f.conv
>> touch -r $f $f.conv
>> mv $f.conv $f
>> done
>>
>> %build
>> %make
>
> %optflags not used.
>
>> %install
>> make install DESTDIR=%{buildroot} \
>
> %makeinstall_std
Here you really need to spefify them, with %makeinstall_std fails
>> libdir=%{_libdir} \
>> usrlibdir=%{_libdir} \
>> exec_prefix=%{_prefix}
>>
> [...]
>> optidesk.spec
>>
>>
>> Name: optidesk
>> Summary: Tool to configure .desktop files to run with optirun
>> Group: Graphical desktop/Other
>> Version: 0.1
>> Release: 1
>> URL: https://github.com/Bumblebee-Project/optidesk
>> License: GPLv3
>> # source from git repo git://github.com/Bumblebee-Project/optidesk.git
>> Source0: %{name}.tar.xz
>
> Tarball needs to be versioned.
I did add a comment saying its from git, but i usually use to create a
macro and put some like this:
Source0: %{?git:%{name}}%{!?git:%{name}-%{version}}.tar.xz
but still there isnt any version released
>> Requires: bumblebee
>>
>> %description
>> This tool is intended to be an easy way of configuring your desired
>> applications to be run through Bumblebee. It will allow to create
>> and modify a menu entry with an alternative (Optirun) version of the
>> default launcher.
>>
>> %files
>> %{_bindir}/%{name}
>>
>>
>> %prep
>> %setup -qn %{name}
>>
>> %build
>> autoreconf -fi
>> %configure
>
> %configure2_5x
I also use to use configure2_5X~but here would not make any
difference, but yes here i didnt put because i missed ateention on
this line
>> %make
> [...]
>> %changelog
>> * Mon Mar 19 2012 Simple 3.0-1
>> - initial package
>
> No single-entry changelog needed for imported packages, it will be
> created from the import commit message. (applies to all .specs)
Even so i do add an entry in changelog for my personall reports.
>>
>> dkms-bbswitch.spec
>>
>>
>> %define oname bbswitch
>>
>> Name: dkms-%{oname}
>> Summary: bbswitch - Optimus GPU power switcher
>> Group: System/Kernel and hardware
>> Version: 0.4.1
>> Release: %mkrel 1
>> License: GPLv3
>> URL: https://github.com/Bumblebee-Project/bbswitch
>> # source from git repo git://github.com/Bumblebee-Project/bbswitch.git
>> Source0: %{oname}.tar.xz
>
> Tarball needs to be versioned.
This is from git and already explained that there was no release
>> BuildArch: noarch
>> Requires(post): dkms
>> Requires(preun):dkms
>
> Needs to require dkms.
AFAIK dkms its only used in post and preun scriptlets., so why add
another plain require?
>>
>> %description
>> bbswitch is a kernel module which automatically detects the required
>> ACPI calls for two kinds of Optimus laptops. It has been verified to
>> work with "real" Optimus and "legacy" Optimus laptops (at least, that
>> is how I call them).
>>
>> %files
>> %{_usrsrc}/%{oname}-%{version}/*
>>
>> %post
>> set -x
>> dkms add -m %{oname} -v %{version} --rpm_safe_upgrade || :
>> dkms build -m %{oname} -v %{version} --rpm_safe_upgrade || :
>> dkms install -m %{oname} -v %{version} --rpm_safe_upgrade || :
>> /sbin/modprobe %{oname} || :
>>
>> %preun
>> dkms remove --binary -m %{oname} -v %{version} --rpm_safe_upgrade --all || :
>> /sbin/rmmod %{oname} || :
>>
>
> These scripts are a bit incorrect, see
> https://wiki.mageia.org/en/DKMS_packaging_policy
> (some || : should be replaced with &&)
Well i dont think its incorrect, bow if mageia prefers to use another
code its a different issue.
>> %prep
>> %setup -qn %{oname}
>> sed -i 's/#MODULE_VERSION#/%{version}/g' dkms/dkms.conf
>>
>> %install
>> rm -rf %{buildroot}
>> mkdir -p %{buildroot}%{_usrsrc}/%{oname}-%{version}
>> cp *.c %{buildroot}%{_usrsrc}/%{oname}-%{version}
>> cp Makefile %{buildroot}%{_usrsrc}/%{oname}-%{version}
>> cp dkms/dkms.conf %{buildroot}%{_usrsrc}/%{oname}-%{version}/dkms.conf
>>
>>
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
10.04.2012 07:46, simple w8 kirjoitti:
> Currently i dont have any account to be able to comit these new
> packages for the distro so i ask if someone can review the specs so
> that these packages can start existing in the distro, and i also ask
> if theres someone that can help me with mentoring
Reviewed below. However, there looks to be quite a lot of work
remaining, so I don't think I'll be able to help you personally with the
issues. I hope you'll find a mentor who'll help you through.
> Name: libbsd
> Summary: Library providing BSD-compatible functions for portability
>[...]
> %{_libdir}/libbsd.so.%{major}*
[...]
> %{_libdir}/libbsd.so
[...]
We already have libbsd.a from glibc-devel, which would conflict with
this. If they are really different libraries, something drastic would
have to be done (e.g. renaming or dropping one). I suspect they are the
same, though, in which case this isn't needed.
> %prep
> %setup -q
> # fix encoding of flopen.3 man page
> for f in src/flopen.3; do
> iconv -f iso8859-1 -t utf-8 $f >$f.conv
> touch -r $f $f.conv
> mv $f.conv $f
> done
>
> %build
> %make
%optflags not used.
> %install
> make install DESTDIR=%{buildroot} \
%makeinstall_std
> libdir=%{_libdir} \
> usrlibdir=%{_libdir} \
> exec_prefix=%{_prefix}
>
[...]
> optidesk.spec
>
>
> Name: optidesk
> Summary:Tool to configure .desktop files to run with optirun
> Group: Graphical desktop/Other
> Version:0.1
> Release:1
> URL:https://github.com/Bumblebee-Project/optidesk
> License:GPLv3
> # source from git repo git://github.com/Bumblebee-Project/optidesk.git
> Source0: %{name}.tar.xz
Tarball needs to be versioned.
> Requires: bumblebee
>
> %description
> This tool is intended to be an easy way of configuring your desired
> applications to be run through Bumblebee. It will allow to create
> and modify a menu entry with an alternative (Optirun) version of the
> default launcher.
>
> %files
> %{_bindir}/%{name}
>
>
> %prep
> %setup -qn %{name}
>
> %build
> autoreconf -fi
> %configure
%configure2_5x
> %make
[...]
> %changelog
> * Mon Mar 19 2012 Simple 3.0-1
> - initial package
No single-entry changelog needed for imported packages, it will be
created from the import commit message. (applies to all .specs)
>
> dkms-bbswitch.spec
>
>
> %define oname bbswitch
>
> Name: dkms-%{oname}
> Summary:bbswitch - Optimus GPU power switcher
> Group: System/Kernel and hardware
> Version:0.4.1
> Release:%mkrel 1
> License:GPLv3
> URL:https://github.com/Bumblebee-Project/bbswitch
> # source from git repo git://github.com/Bumblebee-Project/bbswitch.git
> Source0:%{oname}.tar.xz
Tarball needs to be versioned.
> BuildArch:noarch
> Requires(post): dkms
> Requires(preun):dkms
Needs to require dkms.
>
> %description
> bbswitch is a kernel module which automatically detects the required
> ACPI calls for two kinds of Optimus laptops. It has been verified to
> work with "real" Optimus and "legacy" Optimus laptops (at least, that
> is how I call them).
>
> %files
> %{_usrsrc}/%{oname}-%{version}/*
>
> %post
> set -x
> dkms add -m %{oname} -v %{version} --rpm_safe_upgrade || :
> dkms build -m %{oname} -v %{version} --rpm_safe_upgrade || :
> dkms install -m %{oname} -v %{version} --rpm_safe_upgrade || :
> /sbin/modprobe %{oname} || :
>
> %preun
> dkms remove --binary -m %{oname} -v %{version} --rpm_safe_upgrade --all || :
> /sbin/rmmod %{oname} || :
>
These scripts are a bit incorrect, see
https://wiki.mageia.org/en/DKMS_packaging_policy
(some || : should be replaced with &&)
> %prep
> %setup -qn %{oname}
> sed -i 's/#MODULE_VERSION#/%{version}/g' dkms/dkms.conf
>
> %install
> rm -rf %{buildroot}
> mkdir -p %{buildroot}%{_usrsrc}/%{oname}-%{version}
> cp *.c %{buildroot}%{_usrsrc}/%{oname}-%{version}
> cp Makefile %{buildroot}%{_usrsrc}/%{oname}-%{version}
> cp dkms/dkms.conf %{buildroot}%{_usrsrc}/%{oname}-%{version}/dkms.conf
>
> %changelog
> * Mon Mar 19 2012 Simple 0.4.1-1
> - initial package
>
>
> bumblebee.spec
>
>
> Name: bumblebee
> Summary:Bumblebee - support for NVidia Optimus laptops on Linux!
> Group: System/Kernel and hardware
> Version:3.0
> Release:1
Missing %mkrel.
> URL:https://github.com/Bumblebee-Project/bumblebee
> License:GPLv3
Incorrect license, see license policy:
https://wiki.mageia.org/en/Licensing_policy
AFAICS should be GPLv3+. I didn't check other packages, they may have
wrong tags as well.
> # source from git repo git://github.com/Bumblebee-Project/Bumblebee.git
> Source0: Bumblebee.tar.xz
Needs to be versioned.
> BuildRequires:X11-devel
> BuildRequires:pkgconfig(glib-2.0)
> BuildRequires:pkgconfig(libbsd)
> BuildRequires:help2man
> Requires(pre):update-alternatives
> Requires(pos
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/10 simple w8 : > 2012/4/10 Dimitrios Glentadakis : >> >> >>> >>> 2012/4/10 simple w8 : >>> > Hi, >>> > >>> > I see that in Mageia theres no bumblebee packages and these are very >>> > usefull to enable the Nvidia GPU in hibrid machines (machines that >>> > have 2 grapphic cards), please read >>> > https://github.com/Bumblebee-Project >>> > >>> > Currently i dont have any account to be able to comit these new >>> > packages for the distro so i ask if someone can review the specs so >>> > that these packages can start existing in the distro, and i also ask >>> > if theres someone that can help me with mentoring :) >>> > >>> > The specs are attached. >> >> >> >> >> Στις 10 Απριλίου 2012 9:12 π.μ., ο χρήστης Funda Wang >> έγραψε: >> >>> I guess it is a bit later for mga2. I think the feature could be hold >>> till cauldron reopen for mga 3. >> >> >> >> >> Is it related to this bug ? >> https://bugs.mageia.org/show_bug.cgi?id=1748 >> >>. >> -- >> Dimitrios Glentadakis >> > > Seams so, so far wasnt there any bumblebee pckages in mageia By the way these packages were tested for a week and now im able to put the Nvidia GPU running.
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
2012/4/10 Dimitrios Glentadakis : > > >> >> 2012/4/10 simple w8 : >> > Hi, >> > >> > I see that in Mageia theres no bumblebee packages and these are very >> > usefull to enable the Nvidia GPU in hibrid machines (machines that >> > have 2 grapphic cards), please read >> > https://github.com/Bumblebee-Project >> > >> > Currently i dont have any account to be able to comit these new >> > packages for the distro so i ask if someone can review the specs so >> > that these packages can start existing in the distro, and i also ask >> > if theres someone that can help me with mentoring :) >> > >> > The specs are attached. > > > > > Στις 10 Απριλίου 2012 9:12 π.μ., ο χρήστης Funda Wang > έγραψε: > >> I guess it is a bit later for mga2. I think the feature could be hold >> till cauldron reopen for mga 3. > > > > > Is it related to this bug ? > https://bugs.mageia.org/show_bug.cgi?id=1748 > >. > -- > Dimitrios Glentadakis > Seams so, so far wasnt there any bumblebee pckages in mageia
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
> 2012/4/10 simple w8 : > > Hi, > > > > I see that in Mageia theres no bumblebee packages and these are very > > usefull to enable the Nvidia GPU in hibrid machines (machines that > > have 2 grapphic cards), please read > > https://github.com/Bumblebee-Project > > > > Currently i dont have any account to be able to comit these new > > packages for the distro so i ask if someone can review the specs so > > that these packages can start existing in the distro, and i also ask > > if theres someone that can help me with mentoring :) > > > > The specs are attached. > Στις 10 Απριλίου 2012 9:12 π.μ., ο χρήστης Funda Wang έγραψε: > I guess it is a bit later for mga2. I think the feature could be hold > till cauldron reopen for mga 3. > Is it related to this bug ? https://bugs.mageia.org/show_bug.cgi?id=1748 -- Dimitrios Glentadakis
Re: [Mageia-dev] bumblebee in mageia (and mentoring)
I guess it is a bit later for mga2. I think the feature could be hold till cauldron reopen for mga 3. 2012/4/10 simple w8 : > Hi, > > I see that in Mageia theres no bumblebee packages and these are very > usefull to enable the Nvidia GPU in hibrid machines (machines that > have 2 grapphic cards), please read > https://github.com/Bumblebee-Project > > Currently i dont have any account to be able to comit these new > packages for the distro so i ask if someone can review the specs so > that these packages can start existing in the distro, and i also ask > if theres someone that can help me with mentoring :) > > The specs are attached.
[Mageia-dev] bumblebee in mageia (and mentoring)
Hi, I see that in Mageia theres no bumblebee packages and these are very usefull to enable the Nvidia GPU in hibrid machines (machines that have 2 grapphic cards), please read https://github.com/Bumblebee-Project Currently i dont have any account to be able to comit these new packages for the distro so i ask if someone can review the specs so that these packages can start existing in the distro, and i also ask if theres someone that can help me with mentoring :) The specs are attached. libbsd.spec Description: Binary data optidesk.spec Description: Binary data dkms-bbswitch.spec Description: Binary data bumblebee.spec Description: Binary data bumblebee-ui.spec Description: Binary data dkms-acpi_call.spec Description: Binary data libindicator.spec Description: Binary data virtualgl.spec Description: Binary data
