Re: Proposal to do regular jenkins updates via jessie-updates
Hi,
Adam D. Barratt a...@adam-barratt.org.uk writes:
On Wed, 2015-04-08 at 23:33 +0200, Niels Thykier wrote:
On 2015-04-08 22:45, Miguel Landaeta wrote:
Do you think is feasible or acceptable to maintain Jenkins in
jessie-updates suite instead?
I am not entirely convinced that Jenkins applies to stable-updates
criteria[1]. However, I am leaving the final call on that to the SRMs.
As someone who was involved in the initial setup of stable-updates, I'm
afraid that I'm not convinced either.
[...]
https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line suggests
that long-term means supported for three months. I'm struggling to
combine those two ideas, particularly in the context of a Debian stable
release. (Similarly battle-tested — meaning those commits that have
already been a part of a main line release for more than a week.)
I do wonder whether backports might be suitable, but I can't and won't
speak on behalf of the backports team.
From my understanding, packages in ${x}-backports must be included in
the ${x+1} release. For a package like Jenkins this currently doesn't
seem possible, so it cannot go to backports either.
So it looks to me like we currently miss a place to offer a package like
Jenkins to stable users, but it would be nice to have one as I believe
there will be more packages in this situation in the future (even though
we might not like this).
I do wonder a bit how much this is different from Iceweasel or Chromium
however: there we also ship new upstream releases to stay at a supported
version (though the life-time for Jenkins seems even shorter). Of course
this only works as long as no new dependencies are pulled in, or at
least stay at something managable.
Ansgar
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87oamx203n@deep-thought.43-1.org
Re: Proposal to do regular jenkins updates via jessie-updates
On 2015-04-09 9:10, Ansgar Burchardt wrote: [...] So it looks to me like we currently miss a place to offer a package like Jenkins to stable users, but it would be nice to have one as I believe there will be more packages in this situation in the future (even though we might not like this). I do wonder a bit how much this is different from Iceweasel or Chromium however: there we also ship new upstream releases to stay at a supported version (though the life-time for Jenkins seems even shorter). Of course this only works as long as no new dependencies are pulled in, or at least stay at something managable. AIUI we do that because it's the only way to get security updates for either package, which is why they're shipped via the security archive; likewise openjdk and mysql. Regards, Adam -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/f0b308a94277e59081ac7f49a3a80...@mowgli.jungle.funky-badger.org
Re: Proposal to do regular jenkins updates via jessie-updates
Le 09/04/2015 10:10, Ansgar Burchardt a écrit : Of course this only works as long as no new dependencies are pulled in, or at least stay at something managable. Jenkins upgrades have been accompanied by new dependencies in the past, the upstream developers often refactor the code and split some parts off the core into separate modules. And the recent security update requires a new library (script-security-plugin). So if we were to support Jenkins through jessie-updates we have to be prepared to accept new packages as well (and hope that our toolchain is still able to build them in Jessie). Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/552640f5.5080...@apache.org
Re: RFS: jnr-ffi, jnr-enxio and jnr-unixsocket
On Thu, 9 Apr 2015 03:17:12 +, Tim Potter escribió: [...] Done - I updated d/copyright and also submitted a patch to upstream adding them where missing. I just uploaded the package. I added another missing snippet to d/copyright file. There were some .java files from Guava project. Thanks for your contribution. PS. Upstream recently released jnr-ffi 2.0.2. Do you plan to package this release soon? -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. Faith means not wanting to know what is true. -- Nietzsche signature.asc Description: Digital signature
Re: Proposal to do regular jenkins updates via jessie-updates (Was: Re: Removing Jenkins from Jessie)
Hi, On Mittwoch, 8. April 2015, Niels Thykier wrote: * There are several jenkins-* packages that will (presumably) need to be updated as often as Jenkins itself. I wondered which packages were jenkins* and figured it out with the help from Adam: holger@coccia:~$ dak rm -Rn jenkins Will remove the following packages from unstabl jenkins | 1.565.3-3 | source, all jenkins-cli | 1.565.3-3 | all jenkins-common | 1.565.3-3 | all jenkins-external-job-monitor | 1.565.3-3 | all jenkins-slave | 1.565.3-3 | all jenkins-tomcat | 1.565.3-3 | all libjenkins-java | 1.565.3-3 | all libjenkins-plugin-parent-java | 1.565.3-3 | al Maintainer: Debian Java Maintainers pkg-java-m --- Reason --- -- Checking reverse dependencies... # Broken Build-Depends: jenkins-ant-plugin: libjenkins-plugin-parent-java jenkins-antisamy-markup-formatter-plugin: libjenkins-plugin-parent-java jenkins-instance-identity: libjenkins-plugin-parent-java jenkins-mailer-plugin: libjenkins-plugin-parent-java jenkins-matrix-auth-plugin: libjenkins-plugin-parent-java jenkins-matrix-project-plugin: libjenkins-plugin-parent-java jenkins-ssh-cli-auth: libjenkins-plugin-parent-java Dependency problem found. cheers, Holger, wo is used to install jenkins from upstream but likes installing jenkins-job-builder from main and hopefully soon jenkins-debian-glue packages too... signature.asc Description: This is a digitally signed message part.
