Hi all,
Since there is no consensus to maintain a subset of Jenkins I'll proceed
with its removal (#811522). I'll also request the removal of the Jenkins
specific libraries. Here is the list of packages I've identified, let me
know if there are others:
access-modifier-checker
bytecode-compati
Le 24/01/2016 16:54, 殷啟聰 a écrit :
> So if my understanding is right, Jenkins is highly likely to be
> removed from Debian. And the reason behind this is because the release
> cycle of Jenkins is way too short and upstream already provides .deb?
Yes that's correct. The security fixes for Jenkins
Hi,
Am 24.01.2016 um 16:54 schrieb 殷啟聰:
> Hi,
>
> So if my understanding is right, Jenkins is highly likely to be
> removed from Debian. And the reason behind this is because the release
> cycle of Jenkins is way too short and upstream already provides .deb?
Upstream has a so called LTS Release
Hi Kai-Chung Yan,
I don't have an answer to your question but I would like to point out
that gradle [1] does not depend on SBT [2]. They do similar things but
SBT is Scala oriented while Gradle aims to be a more generic build tool.
Regarding your question, from my experience during Debconf Heidle
Hi,
So if my understanding is right, Jenkins is highly likely to be
removed from Debian. And the reason behind this is because the release
cycle of Jenkins is way too short and upstream already provides .deb?
So this makes me think about what exactly should be packaged into
Debian. There are not
Le 14/01/2016 10:15, Thorsten Glaser a écrit :
> Hrm, so is upstream’s packaging any good then? I have seen
> so many attempts of upstream to package “for” Debian that
> I don’t believe them unseen any more…
Reproducibility put aside the upstream package is quite good. The
dependencies and the pa
Hi,
On Thu, Jan 14, 2016 at 10:15:36AM +0100, Thorsten Glaser wrote:
> On Thu, 14 Jan 2016, Emmanuel Bourg wrote:
>
> > Thank you for the feedback, I'm glad to hear that at least one person
> > found our work useful.
>
> I indeed do, yes.
>
> > Technically you could achieve the same stability by
On Thu, 14 Jan 2016, Emmanuel Bourg wrote:
> Thank you for the feedback, I'm glad to hear that at least one person
> found our work useful.
I indeed do, yes.
> Technically you could achieve the same stability by installing the
> upstream package once and disabling the jenkins-ci entry in
> /etc/
Le 13/01/2016 19:10, Thorsten Glaser a écrit :
> I’m running a Debian system with the packaged version of Jenkins,
> and I’d be most annoyed if you did…
>
> … because what’s there may be old, but at least it doesn’t break
> every day, and it works just fine.
Hi Thorsten,
Thank you for the feedb
On Mon, 11 Jan 2016, Emmanuel Bourg wrote:
I’m running a Debian system with the packaged version of Jenkins,
and I’d be most annoyed if you did…
> 3. Remove Jenkins completely.
… because what’s there may be old, but at least it doesn’t break
every day, and it works just fine.
Thanks,
//mirabilo
On 2016-01-11
> I believe we should either answer their expectations or do nothing at all.
It is not about either black or white. So allow grey.
signature.asc
Description: Digital signature
On Mon, 2016-01-11 at 21:37 +0100, Emmanuel Bourg wrote:
[...]
> I'm not a user of these packages, so I won't push to keep them if
> nobody supports the idea. But I can see their technical merits over
> the upstream package (better system integration with manpages, bash
> completion, proper daemon
Am 11.01.2016 um 21:37 schrieb Emmanuel Bourg:
> Le 11/01/2016 16:52, Markus Koschany a écrit :
>
>> I presume
>> jenkins-cli and jenkins-slave would be affected by the same short three
>> month support release cycle.
>
> jenkins-cli consists in only 9 classes and requires 4 dependencies
> (commo
Le 11/01/2016 16:52, Markus Koschany a écrit :
> I presume
> jenkins-cli and jenkins-slave would be affected by the same short three
> month support release cycle.
jenkins-cli consists in only 9 classes and requires 4 dependencies
(commons-codec, jenkins-remoting, localizer and trilead-ssh2. It d
ted might
> create a bit of confusion.
>
> Regards,
>
> On 11.01.2016 17:52, Markus Koschany wrote:
>> Am 11.01.2016 um 16:04 schrieb Emmanuel Bourg:
>>> Hi all,
>>>
>>> I'm pondering what we should do about Jenkins in Debian.
>> [...]
&g
d some not supported might
create a bit of confusion.
Regards,
On 11.01.2016 17:52, Markus Koschany wrote:
> Am 11.01.2016 um 16:04 schrieb Emmanuel Bourg:
>> Hi all,
>>
>> I'm pondering what we should do about Jenkins in Debian.
>
> [...]
>
>> 2. Packag
Am 11.01.2016 um 16:04 schrieb Emmanuel Bourg:
> Hi all,
>
> I'm pondering what we should do about Jenkins in Debian.
[...]
> 2. Package a subset of Jenkins.
>We could keep only the jenkins-cli and jenkins-slave package as they
>provide a real added value over th
Hi all,
I'm pondering what we should do about Jenkins in Debian. For the
reminder Jenkins development moves too fast and LTS releases are not
supported long enough to make it suitable for Debian stable. Security
fixes end up being almost impossible to backport properly. Moreover
upstream al
18 matches
Mail list logo
