September 2007 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Quilt setup fails with factory spec files
by Andras Mate 17 Sep '07

17 Sep '07

Hi list, I get some error everytime while extracting the content of source rpm packages from opensuse-factory. I'm using quilt to extract and patch the packages and the same command which works fine on 10.2 packages (quilt setup $SPECFILE) fails on the packages from factory. And the error comes everytime from the same line: "%files lang -f %{name}.lang". An example with the mc package (10.2: 4.6.1-56; 10.3: 4.6.1.135): ===== 10.2: mc/102> quilt setup mc.spec ### md5sum: .....................b......... ### rpmbuild: tpppppppppppppppppppppppppppp Unpacking archive ./mc-4.6.1.tar.bz2 10.3: mc/103> quilt setup mc.spec ### md5sum: .......................b........... ### rpmbuild: The %prep section of mc.spec failed; results may be incomplete 10.3 in verbose mode: mc/103> quilt setup mc.spec -v ... error: Unknown option ? in verify_permissions(:-:) error: line 254: Package does not exist: %files lang -f mc.lang The %prep section of mc.spec failed; results may be incomplete ===== The main difference between the two spec file is in %files section. The %files section from 10.2's package looks like this: ===== %files -f %{name}.lang %defattr(-, root, root) ... ===== The factory spec file: ===== %files %defattr(-, root, root) ... %files lang -f %{name}.lang ===== What would be changed to extract src.rpms with quilt? Or do I need some other additional packages to install if I want work with factory packages? Or a newer version of quilt is needed? Some versions: quilt --version: 0.44, update-desktop-files package version: 10.1-40.8, rpm version 4.4.2 Regards, Andras --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] Re: Quilt setup fails with factory spec files
by Andras Mate 17 Sep '07

17 Sep '07

Hi, inspect says the same: ===== $ /usr/share/quilt/scripts/inspect -v mc.spec md5sum < 00-70-utf8-common.patch md5sum < 00-72-utf8-dialog-title.patch md5sum < 00-73-utf8-bottom-buttons-width.patch md5sum < 00-74-utf8-dialog-filename-truncate.patch md5sum < 00-75-utf8-cmdline-help.patch md5sum < 00-76-utf8-hotlist-highlight.patch md5sum < 00-77-utf8-filename-search-highlight.patch md5sum < 00-78-utf8-filename-search-input.patch md5sum < 00-80-utf8-help-line-drawing-art.patch md5sum < mc-4.6.1-NULL.patch md5sum < mc-4.6.1-apps.patch md5sum < mc-4.6.1-bash-all.patch md5sum < mc-4.6.1-esc-seq.patch md5sum < mc-4.6.1-getpwuid.patch md5sum < mc-4.6.1-long-panel.patch md5sum < mc-4.6.1-no-nb.diff md5sum < mc-4.6.1-palmsupport.patch md5sum < mc-4.6.1-syntax-hpp.patch md5sum < mc-4.6.1-unrar-passwd.patch md5sum < mc-4.6.1-word_docs.patch md5sum < mc-4.6.1-wrapper.patch md5sum < mc-4.6.1-x11browser.diff md5sum < mc-4.6.1.tar.bz2 bzip2 -cd mc-4.6.1.tar.bz2 | md5sum md5sum < mc-CVS-msglen.patch md5sum < mc-CVS-utf8-fix.patch md5sum < mc-CVS-utf8-help.patch md5sum < mc-CVS-utf8-hint.patch md5sum < mc-CVS-utf8-input.patch md5sum < mc-CVS-utf8.patch md5sum < mc-utf8-nlink.patch md5sum < mc-utf8-slang2.patch md5sum < mc.umode_t.patch md5sum < mc.vfs_dirent-offsetof.patch md5sum < x11_browser error: Unknown option ? in verify_permissions(:-:) error: line 254: Package does not exist: %files lang -f mc.lang ===== And rpmbuild sounds like: ===== $ rpmbuild -bp mc.spec error: line 254: Package does not exist: %files lang -f mc.lang ===== Andras >>> Andreas Gruenbacher <agruen(a)suse.de> 09/17/07 6:02 PM >>> On Monday 17 September 2007 17:47, Andras Mate wrote: > 10.3 in verbose mode: > mc/103> quilt setup mc.spec -v > ... > error: Unknown option ? in verify_permissions(:-:) > error: line 254: Package does not exist: %files lang -f mc.lang > The %prep section of mc.spec failed; results may be incomplete > ===== Strange -- quilt setup shouldn't really bother about the files list. Does a simple ``rpmbuild -bp mc.spec'' work? What do you get when running ``/usr/share/quilt/scripts/inspect -v mc.spec''? Thanks, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

Re: [opensuse-packaging] Quilt setup fails with factory spec files
by Andras Mate 17 Sep '07

17 Sep '07

SLES10 >>> Marcus Rueckert <darix(a)web.de> 09/17/07 6:06 PM >>> hi, just curious: what distro are you running on? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] opensuse-packaging@opensuse.org
by Dan Stromberg 15 Sep '07

15 Sep '07

Hi folks. I'm trying to package up a Linus kernel to be used during an autoyast install as the primary kernel for the OS. I have a kernel-source*.rpm built, and I have a kernel-*.rpm built, and I can rpm -ivh them OK. The kernel-*.rpm was easy, but the kernel-source*.rpm was kind of hard - at least by the way I did it. For the kernel-source*.rpm, I started with an openSUSE kernel-source*.rpm, hacked out anything unnecessary-looking, and put in my desired kernel. After much tweaking, it seems to be working - but is there an easier way? Anyway, here's the heart of my question, why I'm posting: I'm not sure what's supposed to update /boot/grub/menu.lst. I know it's happened once for my RPM's, because I can look back in my tty logs and see that it was updated when I cat'd the menu.lst once, but when I rpm -ivh my new RPM's now, menu.lst isn't getting updated. What is supposed to update menu.lst, and what makes it decide when to make a kernel the new default kernel? Also, what is supposed to update the symlinks under /boot? Are these questions better posed on the opensuse-kernel mailing list? Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] [Fwd: [package check i386] sabayon-admin changes]
by Federico Mena Quintero 14 Sep '07

14 Sep '07

Hi, Does anyone know why I get messages like the attached one once per day? :) Is there anything I should change in the Sabayon specfile? I couldn't see anything wrong in it. Thanks, Federico

4 5

[opensuse-packaging] proposal: comment upgrade protection in spec files
by Stanislav Brabec 14 Sep '07

14 Sep '07

Hallo. I want to propose commenting of upgrade protection commands and provides/obsoletes in the spec file and related scripts. If it is not done, it is very complicated to be able to check, whether upgrade protection is still needed or it is completely obsolete. Yes, we may keep these lines in the spec files forever, but it taints our spec files, makes them less readable and sometimes even slower. Proposed: # Name was used in <=OpenSUSE10 and <=SLES10: Provide: oldfoo Obsoletes: oldfoo Quick look at our spec files shows that we have lots of protections for S.u.S.E. Linux 6.2 (1999) -> OpenSUSE 10.3 (2007), but I guess that is is more obsolete than sufficient. Few examples: bibview: Provides: bibvw15 * Fri Jul 14 2000 - werner(a)suse.de - fix bug in annotation handling with update to bibview 2.2 dante: # SuSE series: sec Provides: dantesrv Obsoletes: dantesrv * Mon Dec 04 2000 - mge(a)suse.de - update to 1.1.6, new /etc/init.d handling, long RPM names dx: Provides: dxdata Obsoletes: dxdata * Wed Nov 29 2000 - smid(a)suse.cz - subpackages renamed: dxdoc => dx-doc; dxdata => dx-data ... -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 1

[opensuse-packaging] Next Steps openSUSE 10.3
by Stephan Kulow 10 Sep '07

10 Sep '07

Hi! Just an heads up for the next steps in 10.3 development. Beta 3 was released and has shown still quite some problems. I went through most of the critical+blocker bugs and tried to check if some can be downgraded - unfortunately that wasn't too successful. So there is still plenty to do. So please everyone check and update your release critical bugs. A little reminder: after beta2 we're in "Only major/critical/blocker bugfixes allowed.". Taking that I still see version updates submitted, I don't think everyone knows. I know that every missed version hurts, but we have to draw the line somewhere and we drew it end of august. So please spend your valuable time in testing and fixing what we have instead of enhancing it. Three more things: * The next milestone is friday, Sep 14. After that we're working straight towards RC1, which means after that only fixes for blocker bugs are checked in. So make sure you have your updates for critical and major submitted then. * Every change entry needs to have a bugzilla entry. If there is no bug for a change you think needs to be done, create one assigned to yourself and CC me. * Bugs that won't be fixed for 10.3 can be moved to 11.0 in bugzilla now. I suggest to take that option for every bug you're not planning to do an online update later (should be a minority of the current bugs). Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 6

[opensuse-packaging] Package names for non-openSUSE distributions
by Stefan Dirsch 08 Sep '07

08 Sep '07

Hi Are there any lists for package names for non-openSUSE distributions available? Guessing them for BuildRequires is rather time-consuming. :-( I'm especially interested into X.Org 7 package names for - Debian Etch - Fedora 6 with Extras - Mandriva 2007 - Mandriva 2006 - xUbuntu 7.04 - xUbuntu 6.06 Can I use specfiles for Debian/Ubuntu at all? Is there some magic implemented in the buildservice to convert it to the Debian control file before building? Any HOWTOs available for building Debian/Ubuntu packages with the buildservice? Best regards, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Confusion with build script
by Anders Norrbring 08 Sep '07

08 Sep '07

Hiya! I'm experiencing some problems with the y2pmbuild script, it builds okay, but at the end of every build, before recreating the repository, it shows; /usr/src/packages/pear File `/store1/Archives/SuSE/my_repositary/10.2/repodata/repomd.xml.asc' exists. Overwrite? (y/N) y When I answer 'y', the script exits and I have to rebuild the repo manually. Any ideas on where to look and edit to get rid of this? Anders. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Overwriting debuginfo dependencies
by Michael Schroeder 07 Sep '07

07 Sep '07

Hi Packagers, we added a way to our debuginfo macro to overwrite the standard Requires: %{name} = %{version}-%{release} that gets put into the debuginfo package. You can overwrite it by defining %debug_package_requires, e.g.: - require another package as well: %define debug_package_requires %{name} = %{version}-%{release} perl-debuginfo - require just the version: %define debug_package_requires %{name} = %{version} - require something else: %define debug_package_requires gdb Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1