Mailinglist Archive: opensuse-factory (798 mails)
| < Previous | Next > |
Re: [opensuse-factory] Please trigger rebuild of yast2-apparmor
- From: Ladislav Slezak <lslezak@xxxxxxx>
- Date: Thu, 24 Feb 2011 15:56:37 +0100
- Message-id: <4D6671A5.2060806@suse.cz>
Dne 12.2.2011 00:49, Christian Boltz napsal(a):
I have put the fix into yast2-apparmor-2.20.1 and created SR
to openSUSE:Factory (#62710).
Thank you for the fix!
P.S.: Please, next time rather send the patch to yast-devel@xxxxxxxxxxxx
as we need to put it into SVN so it's not lost after next SVN->OBS check in.
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
Hello,
can someone please trigger the rebuild of yast2-apparmor in Factory?
It contains a perl module in an outdated directory (for the previous
perl version), and a rebuild will put it into the correct directory.
For a longer-term solution, I have added
BuildRequires: perl-macros
%{perl_requires}
to the .spec so that future perl updates trigger a rebuild.
(SR 60630 is on its way to YaST:Head.)
I have put the fix into yast2-apparmor-2.20.1 and created SR
to openSUSE:Factory (#62710).
Thank you for the fix!
P.S.: Please, next time rather send the patch to yast-devel@xxxxxxxxxxxx
as we need to put it into SVN so it's not lost after next SVN->OBS check in.
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak@xxxxxxx
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |