Re: owncloud no longer in wheezy
On Fri, Aug 09, 2013 at 06:07:04AM -0400, Sean Alexandre wrote: I see owncloud is no longer in wheezy, and I'm trying to understand why. Where can I find information on why a package was pulled from a release? I see this, but it only seems to say when it was pulled: http://packages.qa.debian.org/o/owncloud.html It was pulled from testing to unstable on 2013-05-14. I'd like to understand why, (and how this works in general.) Is there somewhere else I can check? I'm trying to understand the Debian development process as much as anything. (I had installed owncloud on a wheezy box when wheezy was testing. I want to install it again, but this time on wheezy stable.) I think I just found the answer to my question, here: http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=nosrc=owncloud#_4_2_5 owncloud 4.0 (the version that was in wheezy testing) had a serious bug. It's been fixed, but in the next release: owncloud 5.0. But, wheezy had already been frozen by that time and so owncloud got pulled. So next time I'll check the Bugs in source package link to understand why a package got pulled from a release: http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=nosrc=owncloud -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130809103357.GA28387@tuzo
Re: owncloud no longer in wheezy
On Fri, Aug 9, 2013 at 7:07 PM, Sean Alexandre s...@alexan.org wrote: I see owncloud is no longer in wheezy, and I'm trying to understand why. Where can I find information on why a package was pulled from a release? I see this, but it only seems to say when it was pulled: http://packages.qa.debian.org/o/owncloud.html It was pulled from testing to unstable on 2013-05-14. I'd like to understand why, (and how this works in general.) Is there somewhere else I can check? searched owncloud debian package wheezy on Google, got this: http://debian.2.n7.nabble.com/Dropping-owncloud-from-Wheezy-td2881142.html Nabble kindly puts the links to the debian archives in: http://lists.debian.org/debian-release/2013/03/msg00042.html In brief, the development on owncloud is really fast-paced at this point. The owncloud developers were maintaining three versions in April and did not have enough core developer manpower to even keep that up. So, it was removed at their suggestion. I'm trying to understand the Debian development process as much as anything. If you can't keep enough developers on it to keep up with security patches, you don't want it in the repositories. (I had installed owncloud on a wheezy box when wheezy was testing. I want to install it again, but this time on wheezy stable.) According to the thread, if things went well, it should be in backports. (I haven't checked.) -- Joel Rees
Re: owncloud no longer in wheezy
Joel Rees: On Fri, Aug 9, 2013 at 7:07 PM, Sean Alexandre s...@alexan.org wrote: (I had installed owncloud on a wheezy box when wheezy was testing. I want to install it again, but this time on wheezy stable.) According to the thread, if things went well, it should be in backports. (I haven't checked.) It isn't. But there's this: $ cat /etc/apt/sources.list.d/owncloud.list deb http://download.opensuse.org/repositories/isv:ownCloud:community/Debian_6.0/ / J. -- If I had to live on a desert island I would take a mobile phone, preferably a Nokia 8810. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: owncloud no longer in wheezy
Am Freitag, 9. August 2013, 13:09:14 schrieb Jochen Spieker: Joel Rees: On Fri, Aug 9, 2013 at 7:07 PM, Sean Alexandre s...@alexan.org wrote: (I had installed owncloud on a wheezy box when wheezy was testing. I want to install it again, but this time on wheezy stable.) According to the thread, if things went well, it should be in backports. (I haven't checked.) It isn't. But there's this: $ cat /etc/apt/sources.list.d/owncloud.list deb http://download.opensuse.org/repositories/isv:ownCloud:community/Debian_6.0 / / Does it need to be in backports? I think a co-worker has installed it from Sid. I think backports are just created for packages that are not installable from Sid. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 signature.asc Description: This is a digitally signed message part.
Re: owncloud no longer in wheezy
Martin Steigerwald grabbed a keyboard and wrote: Does it need to be in backports? That's the preferred location, AFAIK. I think a co-worker has installed it from Sid. I think backports are just created for packages that are not installable from Sid. According to the Backports page at http://backports.debian.org/ - Backports are packages taken from the next Debian release (called testing), adjusted and recompiled for usage on Debian stable. Because the package is also present in the next Debian release, you can easily upgrade your stable+backports system once the next Debian release comes out. In other words, backports packages are specifically compiled and configured for the current stable release (in this case, Wheezy) from the testing (in the case, Sid?) release package. So I'm not sure where you got that idea from. :-) --Dave smime.p7s Description: S/MIME Cryptographic Signature
Re: owncloud no longer in wheezy
Am Freitag, 9. August 2013, 12:11:30 schrieb David Guntner: Martin Steigerwald grabbed a keyboard and wrote: Does it need to be in backports? That's the preferred location, AFAIK. I think a co-worker has installed it from Sid. I think backports are just created for packages that are not installable from Sid. According to the Backports page at http://backports.debian.org/ - Backports are packages taken from the next Debian release (called testing), adjusted and recompiled for usage on Debian stable. Because the package is also present in the next Debian release, you can easily upgrade your stable+backports system once the next Debian release comes out. In other words, backports packages are specifically compiled and configured for the current stable release (in this case, Wheezy) from the testing (in the case, Sid?) release package. David, that doesn´t say anything about my claim. So I'm not sure where you got that idea from. :-) AFAIR as I read several times on debian-backports mailinglist on why a package was not considered for backports, if a package from Sid installs into Stable *without* pulling any additional dependencies from Sid, it is not considered for backports. I do not have any exact references right now, but that is what I remember. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 signature.asc Description: This is a digitally signed message part.
Backports (was Re: owncloud no longer in wheezy)
Martin Steigerwald grabbed a keyboard and wrote: Am Freitag, 9. August 2013, 12:11:30 schrieb David Guntner: In other words, backports packages are specifically compiled and configured for the current stable release (in this case, Wheezy) from the testing (in the case, Sid?) release package. David, that doesn´t say anything about my claim. So I'm not sure where you got that idea from. :-) AFAIR as I read several times on debian-backports mailinglist on why a package was not considered for backports, if a package from Sid installs into Stable *without* pulling any additional dependencies from Sid, it is not considered for backports. I do not have any exact references right now, but that is what I remember. Ok, I'll take your word for it. :-) --Dave smime.p7s Description: S/MIME Cryptographic Signature
