Sync ACK'ed.
--
please sync deluge/1.1.2.dfsg-1 from debian-experimental
https://bugs.launchpad.net/bugs/316305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
Confirmed that package from Debian experimental builds fine in pbuilder
chroot for jaunty.
--
please sync deluge/1.1.2.dfsg-1 from debian-experimental
https://bugs.launchpad.net/bugs/316305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the reply! When do you estimate this will happen?
--
please sync deluge/1.1.2.dfsg-1 from debian-experimental
https://bugs.launchpad.net/bugs/316305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@danny -
Just waiting on an ACK for the sync from some one higher up the food
chain. Don't worry, I can pretty much guarantee this will make it into
Jaunty.
If you're feeling impatient though, I have synced deluge (1.1.2.dfsg-1)
in my PPA:
https://edge.launchpad.net/~andrewsomething/+archive/ppa
I'm just a user trying to get the newest version of Deluge through the
PPA for Jaunty. Is this the right bug? I was just wondering what the
status of this was.
I'm running Jaunty 64-bit and the newest version of Deluge with the PPA
enabled is 1.0.7
Thanks,
.danny
--
please sync deluge/1.1.2.dfs
On Mon, Feb 02, 2009 at 05:58:27PM -, Andrew Starr-Bochicchio wrote:
> Thanks for your work on this. I'd also be interested in working with you
> on this from the Ubuntu side. I got the required version of libtorrent
> synced in and pushed to stay in sync with the change from deluge-
> torren
** Description changed:
Debian changes:
deluge (1.1.2.dfsg-1) experimental; urgency=low
.
* New upstream version.
- upstream tarball has been repackaged due to a problem with the file
deluge/metafile.py, which is released with a non-dfsg free license (in
additi
Hello André,
On Mon, Feb 2, 2009 at 6:18 PM, André Gondim wrote:
> I just want do know why we sync from debian this 1.1.2 version. Why we
> just not mantaner?
Because that's the way it is done. There is no need to do the same
thing twice (packaging work). We regularly sync/merge packages from
Deb
Hi Cristian,
Thanks for your work on this. I'd also be interested in working with you
on this from the Ubuntu side. I got the required version of libtorrent
synced in and pushed to stay in sync with the change from deluge-
torrent to deluge. I should have contacted you before proposing an
update,
** Description changed:
+ Debian changes:
+
+ deluge (1.1.2.dfsg-1) experimental; urgency=low
+ .
+ * New upstream version.
+ - upstream tarball has been repackaged due to a problem with the file
+ deluge/metafile.py, which is released with a non-dfsg free license (in
+ additi
I wrote 1.1.4 but still 1.1.2 sorry.
But we had some people in comunity want do maintainer, why should we do
this?
--
please sync deluge/1.1.2.dfsg-1 from debian-experimental
https://bugs.launchpad.net/bugs/316305
You received this bug notification because you are a member of Ubuntu
Bugs, which
I just want do know why we sync from debian this 1.1.2 version. Why we
just not mantaner?
We had some contributors wanting to do this...
This program had 1.1.4 version now and we will use 1.1.2?
Cheers.
--
please sync deluge/1.1.2.dfsg-1 from debian-experimental
https://bugs.launchpad.net/bugs
12 matches
Mail list logo
