Re: Shared library incompatibilty and versioned build-dependencies
Hi Paul, Paul Wise wrote: > On Mon, May 16, 2011 at 1:07 AM, Matt Kraai wrote: > > > I'm trying to create a new package of The Unarchiver. > > Thanks! > > How are you building it? I took a look and gave up when I saw it has > no makefiles, only an Xcode project and the GNUStep pbxbuild (that > translates Xcode stuff to Makefiles) tool is not available in Debian > yet. There's a Makefile.linux in the XADMaster subdirectory that can build the lsar and unar command line executables. You can find my preliminary packages at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619602 > > When I build it in unstable, it generates the following warning > > and the resulting executables hang when run: > > > > /usr/bin/ld: warning: libobjc.so.2, needed by > > /usr/lib/gcc/x86_64-linux-gnu/4.6.1/../../../../lib/libgnustep-base.so, > > may conflict with libobjc.so.3 > > > > If I build the package in testing, it links only against > > libobjc.so.2 > > and the executables run successfully. I shouldn't upload such a > > package to the archive though, right? > > > > I think that this will be fixed by rebuilding gnustep-base against > > libobjc.so.3. Should I add a versioned dependency against the fixed > > version of libgnustep-base-dev to ensure that the autobuilders use > > the > > right version? > > gnustep-base should definitely be rebuilt against the new ObjC > library. I think you could just wait until the rebuilt gnustep-base is > available everywhere. > > I don't see any objc transition here: > > http://release.debian.org/transitions/ > > You might want to ask the maintainers if they had any plans for a > transition and the release team for a binNMU and if they had noticed > the need for a transition. OK, I'll do so. Thanks for the help, -- Matt Kraai https://ftbfs.org/kraai -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110517025021.gb4...@ftbfs.org
Re: Workflow with debian/ in VCS
Nikolaus Rath writes: > Hmm, but you snipped away step #4: making changes to the debian/* > tree. How do I incorporate that into the workflow? You just, um, do it? I don't know why that would be different. > >> 6. Copy debian back into repo > > > Ben Finney writes: > > [copying the ‘debian/’ directory in and out is] obviated by having > > the repositories separate, and automatically combined when needed. > > I don't understand. I can only modify the debian tree when the upstream > sources are present in the same directory (otherwise I can't update > patches) Sure you can update the patches. You make the patches from the VCS repository for the upstream source, just as you'd expect. The only difference is where you place the resulting patch. In my case: $ pwd foo.debian/ $ ( cd ~/Projects/foo/mychanges/ && bzr diff -p 'old/:new/' ../trunk/ ) > debian/patches/03.mychanges.patch Perhaps I'm not understanding you. -- \ “The long-term solution to mountains of waste is not more | `\ landfill sites but fewer shopping centres.” —Clive Hamilton, | _o__)_Affluenza_, 2005 | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ei3yf8wo@benfinney.id.au
RFS: cairomm
Dear mentors, I am looking for a sponsor for the package "cairomm". * Package name: cairomm Version : 1.10.0-1.1 Section : libs It builds these binary packages: libcairomm-1.0-1 - C++ wrappers for Cairo (shared libraries) libcairomm-1.0-dev - C++ wrappers for Cairo (development files) libcairomm-1.0-doc - C++ wrappers for Cairo (documentation) The package appears to be lintian clean. My motivation for maintaining this package is: bringing gnome3 to debian and this package is needed for gtkmm. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/c/cairomm - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/c/cairomm/cairomm_1.10.0-1.1.dsc I would be glad if someone uploaded this package for me. Kind regards Thomas Bechtold signature.asc Description: This is a digitally signed message part
mercurial-buildpackage question
Hello, I'm having some trouble with mercurial-buildpackage. I prepared a hg repository that contains just my initial debian/ directory. Then I imported the upstream source with mercurial-importorig, and tried to run mercurial-pristinetar for testing. However, $ mercurial-importorig ../python-llfuse_0.31.orig.tar.bz2 I: Remember to quilt push -a and sort out any problems. I: After that, commit everything including .pc directory. $ rm ../python-llfuse_0.31.orig.tar.bz2 $ mercurial-pristinetar E: xdelta patch -p python-llfuse_0.31.orig.tar.xdelta recreated-python-llfuse_0.31.orig.tar python-llfuse_0.31.orig.tar failed: E: xdelta: python-llfuse_0.31.orig.tar: Checksum validation failed, expected: 46b0654f58658909c94c0cbebe3ec85d, received: 224626f778961d46651bdbd9e888d51e E: xdelta: recreated-python-llfuse_0.31.orig.tar: Checksum validation failed, expected: 04f0920de545408e6d6d6c71c44ac72e, received: 485974fdef8fac7bae55acf123052e00 Why isn't this working? Thanks, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87zkmmd04m@inspiron.ap.columbia.edu
RFS: atom4 (updated package)
Dear mentors, I am looking for a sponsor for the new version 4.1-5.1 of the package "atom4". It builds these binary packages: atom4 - An original two-player color puzzle game The upload would fix these bugs: 617839 (This upload is a NMU intended to fix a FTBFS bug) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/a/atom4 - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/a/atom4/atom4_4.1-5.1.dsc I would be glad if someone uploaded this package for me. Kind regards, -- Bhavani Shankar Ubuntu Developer | www.ubuntu.com https://launchpad.net/~bhavi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTitdGhs5J9FyE-m7O¨smtop...@mail.gmail.com
Re: Workflow with debian/ in VCS
Ben Finney writes:
>> I'm having trouble coming up with a decent workflow for creating
>> packages. I am managing the debian/ directory in a mercurial
>> repository,
>
> Contrary to other replies in this thread, I find that to be a cleaner
> setup: manage just ‘debian/’ in a VCS repository, and build packages
> with ‘${VCS}-buildpackage’.
>
>> and at the moment my steps for releasing a new version are:
>>
>> 1. Download the new upstream source
>> 2. Rename to .orig.tar.bz2, extract, rename created directory
>
> These two steps should be automated with ‘uscan(1)’. Configure it for
> your package with the ‘debian/watch’ file.
>
>> 3. Copy debian/ from repo into extracted directory
>> 5. Run debuild
>
> These two steps are what ‘${VCS}-buildpackage’ does. You don't have to
> have the build artefacts cluttering up your working tree; it does its
> work elsewhere.
Hmm, but you snipped away step #4: making changes to the debian/* tree.
How do I incorporate that into the workflow?
>> 6. Copy debian back into repo
>
> Obviated by having the repositories separate, and automatically combined
> when needed.
I don't understand. I can only modify the debian tree when the upstream
sources are present in the same directory (otherwise I can't update
patches), so I have to either extract the upstream source in the VCS
tree, or copy the modified debian directory back into the repo.
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87pqnilisi@inspiron.ap.columbia.edu
RFS: libpam-abl
Dear mentors, I am looking for a sponsor for my package "libpam-abl". * Package name: libpam-abl Version : 0.4.1-1 Upstream Author : Chris Tasma , Andy Armstrong * URL : http://pam-abl.deksai.com/ * License : GPL2 Section : admin It builds these binary packages: libpam-abl - pam_abl blocks hosts which are attempting a brute force attack. The package appears to be lintian clean. The upload would fix these bugs: 356733 , 333081 My motivation for maintaining this package is: I use this software for a long time and wondering why it is not available in Debian . I've found old IPT and RFP bugs for it and decided to create the package . The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libpam-abl - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libpam-abl/libpam-abl_0.4.1-1.dsc I would be glad if someone uploaded this package for me. Kind regards Alex Mestiashvili
Re[2]: RFS: manaplus
Mon, 16 May 2011 10:52:04 +0800 письмо от Paul Wise : > On Mon, May 16, 2011 at 1:22 AM, andrei karas wrote: > > > Section : games > > You might want to join the Debian games team and help out with other games > too: > > http://wiki.debian.org/Games/Team > > Jump on our IRC channel and we will walk you through the process. > > We are also having another meeting soon, I would encourage you to come. Ok, i will try search time to see it. > > manaplus - Extended client for The Mana World and similar servers > > We already have two versions of The Mana World in Debian (tmw and > mana), is there any reason you couldn't just merge manaplus into one > of them? CCing the maintainer of tmw and mana, perhaps he can shed > some light onto the situation. I wonder why there needs to be two > versions of the same game. If i remember correctly will be one version. By request from upstram tmw will be branded package for mana (desktop file, background etc) Manaplus is fork of tmw/mana. Code is different, data files not very different, but in manaplus more data. Manaplus have many more features. Possible more faster and stable code. Some or all this features impossible add to mana client by different reasons. In tmw server manaplus used by most power players. Also manaplus developed for support not released server, forked from server, what used now in tmw.
