[Bug 116709] Re: Backport of rhythmbox 0.10.90
the new 0.11.0 release b/i/r fine with prevu -- Backport of rhythmbox 0.10.90 https://bugs.launchpad.net/bugs/116709 You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for Feisty Backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 116709] Re: Backport of rhythmbox 0.10.90
rhythmbox 0.11.0 has been released. I'm building ti right now, so i cannot say b/r/i yet, though, it looks good, and as the 0.10.90 release is almost identical, i wouldn't expect any breakage. will update shortly. -- Backport of rhythmbox 0.10.90 https://bugs.launchpad.net/bugs/116709 You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for Feisty Backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Re: [Bug 112511] Re: Backport Pidgin 2.0.0 Final to Fiesty
-- Matt Nicholson [EMAIL PROTECTED] On 5/28/07, Mahdi <[EMAIL PROTECTED]> wrote: > > I guess it should be backported as fast as possible. > Feisty is a final (stable) release, and the amount of beta packages on it > should be minimized. And since gaim is no longer "mantained" (only pidgin), > it sould be a good idea to backport the latest stable release it to get > upstream support (and also a more stable version). > > I don't think we should wait for all the plugins to be released for > pidgin since most of the people doesn't use any of them at all or only 2 > or 3 (like guifications and extended prefs). Anyway, I think most of the > users will be happy only with plain pidgin. And i really think some of > the plugins will now be discontinued. And finally I don't consider "not > backporting some plugins" a package breakage. All those plugins are > recommends or suggests, not depends. Anyone who really needs a certain > not-backported plugin should stick to gaim anyway. > > I guess backporting pidgin to feisty is only a matter of removing gaim > from ubuntu-desktop (or changing it to "gaim | pidgin") and repackaging > it. Some upgrades might be necessary but i think people are already > working on that. acctually, when building pedgin in prevu, a gaim*>deb is generated, for the sole purpose of allowing upgrades. since ubuntu-desktop depends on gaim, and the new gaim package is nothing , or than depending on pidgin (well it cleans up some things i think), the upgrade path is clean, and doesn't require ubuntu-desktop etc to be rebuilt. -- > Backport Pidgin 2.0.0 Final to Fiesty > https://bugs.launchpad.net/bugs/112511 > You received this bug notification because you are a direct subscriber > of the bug. > -- Backport Pidgin 2.0.0 Final to Fiesty https://bugs.launchpad.net/bugs/112511 You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for Feisty Backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 116709] Backport of rhythmbox 0.10.90
Public bug reported: a whole bunch of nice updates, including nicer icons and some UI improvements. b/i/r just fine from prevu for me ** Affects: feisty-backports (upstream) Importance: Undecided Status: Unconfirmed -- Backport of rhythmbox 0.10.90 https://bugs.launchpad.net/bugs/116709 You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for Feisty Backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 112511] Re: Backport Pidgin 2.0.0 Final to Fiesty
after successfully backporting evolution-data-server (see https://bugs.launchpad.net/feisty-backports/+bug/114031), pidgin built without a hitch in prevu, and is running without a problem on my workstation right now. it even provides a gaim meta/transition package to help the upgrade path. b/i/r +1 -- Backport Pidgin 2.0.0 Final to Fiesty https://bugs.launchpad.net/bugs/112511 You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for Feisty Backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 114031] libebook1.2-9 (needed for pidgin backporting)
Public bug reported: or rather, evolution-data-server (1.11.1-0ubuntu2) (which generates the package), is needed to successfully backport pidgin. b/i/r just fine from prevu, and am running it now on my feisty box, without issues (using evolution without any problems) ** Affects: feisty-backports (upstream) Importance: Undecided Status: Unconfirmed -- libebook1.2-9 (needed for pidgin backporting) https://bugs.launchpad.net/bugs/114031 You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for Feisty Backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 112511] Re: Backport Pidgin 2.0.0 Final to Fiesty
Just tried in prevu now that pidgin hit the repos, fails with: -> Considering build-dep libebook1.2-dev -> Trying libebook1.2-dev -> Cannot install libebook1.2-dev; apt errors follow: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libebook1.2-dev: Depends: libebook1.2-9 (= 1.10.1-0ubuntu1) but it is not going to be installed libnss3-dev: Depends: libnspr4-dev (= 1.8.0.10-3ubuntu1) but it is not going to be installed E: Broken packages E: Could not satisfy build-dependency. I built it from source (well, not ubuntu source, but the orig source fine, so i'm going to take a few looks around and see what can be done about this.) -- Backport Pidgin 2.0.0 Final to Fiesty https://bugs.launchpad.net/bugs/112511 You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for Feisty Backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 75390] Re: f-spot 0.30
+1, b/i/r in prevu fine. -- f-spot 0.30 https://launchpad.net/bugs/75390 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 75761] Re: libgpod 0.4.0
I've been using this, along with a prevu'd rhythmbox 0.9.7 with no issues for 5 days now. The new features of rhythmbox are, in my opinion, worth it. This is the only thing holding rhythmbox back from being backported. ** Changed in: edgy-backports (upstream) Status: Rejected => Unconfirmed -- libgpod 0.4.0 https://launchpad.net/bugs/75761 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 75761] libgpod 0.4.0
Public bug reported: needed for the upcomming (this weekend?) release of rhythmbox 0.9.7 ** Affects: edgy-backports (upstream) Importance: Undecided Status: Unconfirmed -- libgpod 0.4.0 https://launchpad.net/bugs/75761 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 75761] Re: libgpod 0.4.0
b/i/"r" from prevu fine. resulting debs: libgpod0_0.4.0-0ubuntu3~6.10prevu1_i386.deb libgpod-common_0.4.0-0ubuntu3~6.10prevu1_all.deb libgpod-dev_0.4.0-0ubuntu3~6.10prevu1_i386.deb -- libgpod 0.4.0 https://launchpad.net/bugs/75761 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 75482] Re: banshee 0.11.3
Okay, forget all about those build errors. I had been playing around with some evn variable to run some paralell make commands and ran into something similar while building the rhythmbox release canidate. i think one process was looking for something the other hadn't finished yet. as soon as i reverted all my problems went away. in any case, banshee 0.11.3 just built, installed, and runs fine from prevu on edgy. sorry for all the confusion. -- banshee 0.11.3 https://launchpad.net/bugs/75482 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 75482] Re: banshee 0.11.3
oh, i had previously backported cli-common-dev to build beagle, after doing so, the above error/build breakage occurs (looks like in taglib- sharp) -- banshee 0.11.3 https://launchpad.net/bugs/75482 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 75482] banshee 0.11.3
Public bug reported: theres a good amount of fixes, including a major speed up when switching sources. ** Affects: edgy-backports (upstream) Importance: Undecided Status: Unconfirmed -- banshee 0.11.3 https://launchpad.net/bugs/75482 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 75482] Re: banshee 0.11.3
Compiles from source fine on my edgy desktop (no major
modifications/changes), however, in prevu it fails with:
Making all in taglib-sharp
make[3]: Entering directory
`/var/cache/prevu/src/5206/banshee-0.11.3+dfsg/taglib-sharp'
/usr/bin/gmcs -debug -nowarn:0278 -target:library -out:TagLib.dll -r:Mono.Posix
./TagLib/*.cs ./TagLib/*/*.cs ./TagLib/*/*/*.cs
make[3]: *** No rule to make target `TagLib.dll.mdb', needed by `all-am'. Stop.
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory
`/var/cache/prevu/src/5206/banshee-0.11.3+dfsg/taglib-sharp'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/cache/prevu/src/5206/banshee-0.11.3+dfsg'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/cache/prevu/src/5206/banshee-0.11.3+dfsg'
make: *** [debian/stamp-makefile-build] Error 2
Copying back the cached apt archive contents
-> unmounting dev/pts filesystem
-> unmounting proc/sys/fs/binfmt_misc filesystem
-> unmounting proc filesystem
-> unmounting /var/cache/prevu/edgy-debs filesystem
-> unmounting /var/cache/prevu/src/5206 filesystem
-> cleaning the build env
-> removing directory /var/cache/prevu/builds/5310 and its subdirectories
Traceback (most recent call last):
File "/usr/bin/prevu", line 146, in ?
BackportFromAPT(sys.argv[1],DIST).backport()
File "/usr/bin/prevu", line 86, in backport
self.do_compile()
File "/usr/bin/prevu", line 67, in do_compile
raise ValueError("Build failed.")
ValueError: Build failed.
** Description changed:
- theres a good amoutn of fixes, including a major speed up when switching
+ theres a good amount of fixes, including a major speed up when switching
sources.
--
banshee 0.11.3
https://launchpad.net/bugs/75482
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 73801] Re: request cairo-clock
+1 builds fine in prevu. runs fine as well. -- request cairo-clock https://launchpad.net/bugs/73801 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
follow up on the web-interface idea
Last month (late Dec.) i submitted an idea for a web based interface for submitting possible backports. basically a user could enter a package name, and some checks would be done to see if teh package can be backported (blacklists, etc) then the system would attempt to backport it. a few other features such as giving the user their binary right away (with warning it hasn't been tested, etc) were given too. i didn't start working on it right away because i was at home for winter break and didn't have good access to my build system/server to start setting up the enviorment. so now i'm back at school, in my software design class, and we have to come up with a project to work on in a 3 person group for teh semester. tons of documentation etc. i'm pretty sick of doing pointless projects for school, so, i would like to do something that would acctually be used. after thinking for a minute, i realized this is something we could do, the web-interface that is. so, has anyone started on this? i just don't want to repeat someone eles work etc. i would, of course be willing to give updates etc, and would want to make everything availible under the gpl or something similar, of course. so, do anyone have any issues with this being done as a project for school this spring? we could do most of our planning early, and, if we get it all done on time, it should be all set to be used for dapper a month or so after release. let me know. ps: any bad spelling/typo's you can contribute to my dislocated thumb. matt nicholson [EMAIL PROTECTED] sjoeboo.com -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
fast-user-switch-applet 2.13.3
built fine and seems to work fine. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Re: totem 1.2.1 question.
never mind, i just built it with the script and both packages, totem-xine and totem-gstreamer were built, along with firefox plugins etc. about to start testing. On Dec 12, 2005, at 1:52 PM, matt nicholson wrote: was looking into backporting it. defaults to xine backend. should 2 versions be built with xine/gstreamer enabled? what would the easiest way to do that be (other than a completely manual ./configure, compile, and package build). thanks. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
totem 1.2.1 question.
was looking into backporting it. defaults to xine backend. should 2 versions be built with xine/gstreamer enabled? what would the easiest way to do that be (other than a completely manual ./configure, compile, and package build). thanks. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
gcolor2_0.4-1
backported fine and runs fine for me. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
easytag 1.99.10
was a forum request. built just fine and is running just fine for me. -- matt nicholson [EMAIL PROTECTED] sjoeboo.com -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
nmap & nessus
were requested in forums. both backported just fine for me. nmap 3.93 nessus 2.2.5 matt nicholson [EMAIL PROTECTED] sjoeboo.com -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
ntop 3.2
was requested in the forums, i just backported it fine. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Re: tango-icon-theme,icon-naming-utils
ah ha, okay then, thanks. On Nov 30, 2005, at 2:20 PM, John Dong wrote: imagemagick cannot be backported, because of its wide use on the system (even php uses imagemagick). On 11/30/05, matt nicholson < [EMAIL PROTECTED]> wrote:just backported them and installed, everything was fine. during the build process, had to backport imagemagick, which yeildedmultiple packages. complete file list: icon-naming-utils_0.5.0-0ubuntu1_all.deb libmagick++9-dev_6.2.4.5-0.3ubuntu1_i386.deb imagemagick_6.2.4.5- 0.3ubuntu1_i386.deb libmagick9-dev_6.2.4.5-0.3ubuntu1_i386.deb libmagick9_6.2.4.5-0.3ubuntu1_i386.deb perlmagick_6.2.4.5-0.3ubuntu1_i386.deb libmagick++9c2a_6.2.4.5-0.3ubuntu1_i386.deb tango-icon-theme_0.5.0-0ubuntu1_all.deb all installed just fine and seem to have 0 issues. --- matt nicholson [EMAIL PROTECTED] sjoeboo.com -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
tango-icon-theme,icon-naming-utils
just backported them and installed, everything was fine. during the build process, had to backport imagemagick, which yeildedmultiple packages. complete file list: icon-naming-utils_0.5.0-0ubuntu1_all.deb libmagick++9-dev_6.2.4.5-0.3ubuntu1_i386.deb imagemagick_6.2.4.5-0.3ubuntu1_i386.deb libmagick9-dev_6.2.4.5-0.3ubuntu1_i386.deb libmagick9_6.2.4.5-0.3ubuntu1_i386.deb perlmagick_6.2.4.5-0.3ubuntu1_i386.deb libmagick++9c2a_6.2.4.5-0.3ubuntu1_i386.deb tango-icon-theme_0.5.0-0ubuntu1_all.deb all installed just fine and seem to have 0 issues. --- matt nicholson [EMAIL PROTECTED] sjoeboo.com -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Re: setting up a backports environment
alright then, that makes it even simpler, thanks. what about the procedure for after the package is built? just notify someone "official" that it builds fine or what? thanks again John, you've been pretty quick and helpfully. matt nicholson [EMAIL PROTECTED] sjoeboo.com On Nov 30, 2005, at 12:17 PM, John Dong wrote: No need to chroot inside pbuilder... Just download a .dsc file from packages.ubuntu.com, and tell pbuilder to build it everything else is done automagically... On 11/30/05, matt nicholson <[EMAIL PROTECTED]> wrote: to ask. i jsut want to make sure i'm going about everything right. for testing i backported deskbar-applet as follows, was just wondering if i was missing anything or what not (i;m obviously new at packaging) got my chroot via pbuilder. login to the chroot. apt-get build-dep deskbar-applet apt-get source deskbar-applet (fetches all sources from dapper repos) cd deskbar-applet-x.x/ dpkg-buildpackage -d leaves me with the .deb, pending ant errors of course. anything else? any suggestions? whats the procedure once the build completes and everything works fine? just notify the list to have someone "official" build it or what? thanks for the help again. matt nicholson [EMAIL PROTECTED] sjoeboo.com On Nov 30, 2005, at 10:00 AM, matthew nicholson wrote: > > > excelent, exactly what i needed to here. > > On Wed, 2005-11-30 at 09:55 -0500, John Dong wrote: >> >> >> On 11/30/05, matthew nicholson <[EMAIL PROTECTED]> wrote: >> hmm, okay. one question regarding pbuilder/ubp-build.py. if >> your using >> ubp-build.py inside the pbuilder chroot..how do you fetch the >> dapper >> source packages? do you just do it by hand, or can you change >> where teh >> sources are fetch from, so its all automatic? >> >> You don't use ubp-build.py inside pbuilder... ubp-build.py >> accomplishes tasks similar to pbuilder, with you in command instead of >> pbuilder inside the chroot. >> >> Either way, configuration of sources is done by adding deb-src lines >> for Dapper, whether it's /etc/apt/sources.list inside the chroot or >> the pbuilder config file. >> >> >> thanks for the help getting set up guys. >> >> matt nicholson >> [EMAIL PROTECTED] >> sjoeboo.com >> >> >> On Wed, 2005-11-30 at 09:19 -0500, John Dong wrote: >>> meh, either way is fine... I've just never really caught on >> to >>> pbuilder... At times I appreciate the speed of the >> unpack-and-hack >>> approach to figuring out what it takes for a package to >> start >>> compiling... >>> >>> I've been playing with Device Mapper's Copy-on-Write >> functionality for >>> making all changes to the chroot temporary. >>> >>> On 11/30/05, Marc Wiriadisastra < [EMAIL PROTECTED]> >> wrote: >>>> On 11/30/05, John Dong <[EMAIL PROTECTED]> wrote: >>>>> google ubp-build.py >>>>> >>>>> I run ubp-build.py inside a chroot, which is >> cleaned fairly >>> frequently. >>>>> As >>>>> long as you don't do stupid things to the chroot, >> it'll >>> stay fairly >>>>> clean... >>>> >>>> How about using PBuilder? it guarantees a clean >> chroot, and >>> is really >>>> handy to use. See >> http://wiki.ubuntu.com/PbuilderHowto for >>>> instructions >>>> >>> +1 from me since I've never had any issues with >> pbuilder and >>> it's create >>> for testing out dependancy's. >>> >>> >>> >>> -- >>> ubuntu-backports mailing list >>> ubuntu-backports@lists.ubuntu.com >>> >> http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports >>> >> -- >> matthew nicholson < [EMAIL PROTECTED]> >> sjoeboo.com >> >> >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.1 (GNU/Linux) >> >> >> iD8DBQBDjbt3IIMh34W/OGsRAv01AKDncTpkIt1M5iAaGcMY6Mvwp9GdewCg5qfA >> uSBTnV+4faTo4kEU9mqiLWk= >> =e4ch >> -END PGP SIGNATURE- >> >> >> -- >> ubuntu-backports mailing list >> ubuntu-backports@lists.ubuntu.com >> http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports >> >> >> > -- > matthew nicholson <[EMAIL PROTECTED]> > sjoeboo.com > -- > ubuntu-backports mailing list > ubuntu-backports@lists.ubuntu.com > http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Re: setting up a backports environment
alright, i think i'm basically set up but just have one more question to ask. i jsut want to make sure i'm going about everything right. for testing i backported deskbar-applet as follows, was just wondering if i was missing anything or what not (i;m obviously new at packaging) got my chroot via pbuilder. login to the chroot. apt-get build-dep deskbar-applet apt-get source deskbar-applet (fetches all sources from dapper repos) cd deskbar-applet-x.x/ dpkg-buildpackage -d leaves me with the .deb, pending ant errors of course. anything else? any suggestions? whats the procedure once the build completes and everything works fine? just notify the list to have someone "official" build it or what? thanks for the help again. matt nicholson [EMAIL PROTECTED] sjoeboo.com On Nov 30, 2005, at 10:00 AM, matthew nicholson wrote: excelent, exactly what i needed to here. On Wed, 2005-11-30 at 09:55 -0500, John Dong wrote: On 11/30/05, matthew nicholson <[EMAIL PROTECTED]> wrote: hmm, okay. one question regarding pbuilder/ubp-build.py. if your using ubp-build.py inside the pbuilder chroot..how do you fetch the dapper source packages? do you just do it by hand, or can you change where teh sources are fetch from, so its all automatic? You don't use ubp-build.py inside pbuilder... ubp-build.py accomplishes tasks similar to pbuilder, with you in command instead of pbuilder inside the chroot. Either way, configuration of sources is done by adding deb-src lines for Dapper, whether it's /etc/apt/sources.list inside the chroot or the pbuilder config file. thanks for the help getting set up guys. matt nicholson [EMAIL PROTECTED] sjoeboo.com On Wed, 2005-11-30 at 09:19 -0500, John Dong wrote: meh, either way is fine... I've just never really caught on to pbuilder... At times I appreciate the speed of the unpack-and-hack approach to figuring out what it takes for a package to start compiling... I've been playing with Device Mapper's Copy-on-Write functionality for making all changes to the chroot temporary. On 11/30/05, Marc Wiriadisastra <[EMAIL PROTECTED]> wrote: On 11/30/05, John Dong <[EMAIL PROTECTED]> wrote: google ubp-build.py I run ubp-build.py inside a chroot, which is cleaned fairly frequently. As long as you don't do stupid things to the chroot, it'll stay fairly clean... How about using PBuilder? it guarantees a clean chroot, and is really handy to use. See http://wiki.ubuntu.com/PbuilderHowto for instructions +1 from me since I've never had any issues with pbuilder and it's create for testing out dependancy's. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- matthew nicholson < [EMAIL PROTECTED]> sjoeboo.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBDjbt3IIMh34W/OGsRAv01AKDncTpkIt1M5iAaGcMY6Mvwp9GdewCg5qfA uSBTnV+4faTo4kEU9mqiLWk= =e4ch -END PGP SIGNATURE- -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- matthew nicholson <[EMAIL PROTECTED]> sjoeboo.com -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Re: Rhythmbox 0.9.2
odd, cause i got the newest libgpod and rhythmbox to build just perfect last night about 30 minutes after it was released, and ran into no issues with updating dbus etc. On Nov 29, 2005, at 11:54 AM, Mike Basinger wrote: It look like libgpod is dependent on libdbus-1-1 (>= 0.50) and libdbus-glib-1-1 (>= 0.50). I'm unsure messing around with the dbus files. Mike -- D. Michael Basinger: [EMAIL PROTECTED] Web: http://www.mikesplanet.net -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Re: Please backport pmount
yay On Nov 9, 2005, at 3:13 PM, Matt Zimmerman wrote: On Wed, Nov 09, 2005 at 03:08:00PM -0500, John Dong wrote: idn, matt, it's been 11 ;) And it exists on the master archive; it'll take a little while to propagate to the mirrors. At any rate, it's open for business. -- - mdz -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
what is probably a question you are sick of being asked.
now, i know UBZ is going on. and i know this question has been asked a few times already, least i would imagine it has been. so, in advance, i'm sorry if they don't want to hear this again. i do not aim to make people pissed, i'm just curious. when/will breezy backports open? i'm not asking about extras (w32codecs, etc) cause i know some of them have been pulled due to legal issues. what i'm asking about is regular backports, like rhythmbox 0.9.1 from dapper, backported to breezy, etc etc etc. the main reason i ask is actually because of rhythmbox (and banshee maybe ). alot of good thing have been happening in rhythmbox as of late and i think people(ie, those whom do not build from cvs/source constantly) would like to have the newest version and all its great new features. plus as far as i know its already in the dapper tree. so, my question, again, is, when, or better yet, will, breezy backports open? is help needed? i would be more than willing to help, so long as someone guided be at least through my first "backport". I can say that the newest rhythmbox is working perfectly on breezy with all of the crazy new features enabled (DAAP, auidoscrobbler support, etc) once again sorry if this has been asked a hundered times, i don't mean to nag, i just haven't found an actual answer, the forums are all speculation as far as i can see. thanks. matt [EMAIL PROTECTED] sjoeboo.com -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
