Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #207290 > unrolled thread

Wondering how long it usually takes for a package to move from stable-p-u

Started byLuke Picciau <lpicciau@connexion.com.au>
First post2019-04-11 05:40 +0200
Last post2019-06-14 10:30 +0200
Articles 9 — 8 participants

Back to article view | Back to linux.debian.user


Contents

  Wondering how long it usually takes for a package to move from  stable-p-u Luke Picciau <lpicciau@connexion.com.au> - 2019-04-11 05:40 +0200
    Re: Wondering how long it usually takes for a package to move from  stable-p-u Jerome BENOIT <sphericaltriangle@rezozer.net> - 2019-04-11 06:40 +0200
      Re: Wondering how long it usually takes for a package to move from  stable-p-u Francisco M Neto <fmneto@fmneto.com.br> - 2019-04-11 15:00 +0200
        Re: Wondering how long it usually takes for a package to move from  stable-p-u Greg Wooledge <wooledg@eeg.ccf.org> - 2019-04-11 15:10 +0200
          Re: Wondering how long it usually takes for a package to move from stable-p-u Pierre Fourès <pierre.foures@gmail.com> - 2019-04-11 16:40 +0200
          Re: Wondering how long it usually takes for a package to move from  stable-p-u David Wright <deblis@lionunicorn.co.uk> - 2019-04-11 17:20 +0200
            Re: Wondering how long it usually takes for a package to move from  stable-p-u Brian <ad44@cityscape.co.uk> - 2019-04-11 19:30 +0200
              Re: Wondering how long it usually takes for a package to move from  stable-p-u Francisco M Neto <fmneto@fmneto.com.br> - 2019-04-11 22:30 +0200
      Re: Wondering how long it usually takes for a package to move from  stable-p-u andreimpopescu@gmail.com - 2019-06-14 10:30 +0200

#207290 — Wondering how long it usually takes for a package to move from stable-p-u

FromLuke Picciau <lpicciau@connexion.com.au>
Date2019-04-11 05:40 +0200
SubjectWondering how long it usually takes for a package to move from stable-p-u
Message-ID<xLyJb-1Jz-1@gated-at.bofh.it>
I have been tracking this package 
https://tracker.debian.org/pkg/ca-certificates-java for about a month 
because the package version 20170929~deb9u1 which is in stable has a bug 
which is blocking my docker image builds. Version 20170929~deb9u2 should 
fix it but the package has been in stable-p-u for a while now. How long 
usually does it take for a package to move from stable-p-u to stable? 
And is there any way I can install just that one package as the newer 
version on debian stretch without changing the repos to testing for the 
whole OS?

[toc] | [next] | [standalone]


#207294

FromJerome BENOIT <sphericaltriangle@rezozer.net>
Date2019-04-11 06:40 +0200
Message-ID<xLzFg-2kQ-7@gated-at.bofh.it>
In reply to#207290
Hello,

On 11/04/2019 05:59, Luke Picciau wrote:
> I have been tracking this package 
> https://tracker.debian.org/pkg/ca-certificates-java for about a month 
> because the package version 20170929~deb9u1 which is in stable has a bug 
> which is blocking my docker image builds. Version 20170929~deb9u2 should 
> fix it but the package has been in stable-p-u for a while now. How long 
> usually does it take for a package to move from stable-p-u to stable?


You have to bear in mind that currently Debian is terminating a cycle.
 
> And is there any way I can install just that one package as the newer 
> version on debian stretch without changing the repos to testing for the 
> whole OS?

I guess that the best you can do is to build your own package from the debian source material.

hth,
Jerome
> 

[toc] | [prev] | [next] | [standalone]


#207307

FromFrancisco M Neto <fmneto@fmneto.com.br>
Date2019-04-11 15:00 +0200
Message-ID<xLHt7-75G-1@gated-at.bofh.it>
In reply to#207294

[Multipart message — attachments visible in raw view] — view raw

On Thu, 2019-04-11 at 08:20 +0400, Jerome BENOIT wrote:
> And is there any way I can install just that one package as the
> > newer 
> > version on debian stretch without changing the repos to testing for
> > the 
> > whole OS?
> 
> I guess that the best you can do is to build your own package from
> the debian source material.

	Alternatively, if the package has been updated in testing you
can download the .deb and install it manually with 'dpkg -i'.

	Not the best approach, but remedies the problem until a better
solution comes along.

HTH
Francisco

-- 
[]'s,

Francisco M Neto <fmneto@fmneto.com.br>

GPG: 4096R/D692FBF0

[toc] | [prev] | [next] | [standalone]


#207308

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-04-11 15:10 +0200
Message-ID<xLHCN-7oM-7@gated-at.bofh.it>
In reply to#207307
On Thu, Apr 11, 2019 at 09:51:11AM -0300, Francisco M Neto wrote:
> On Thu, 2019-04-11 at 08:20 +0400, Jerome BENOIT wrote:
> > And is there any way I can install just that one package as the
> > > newer 
> > > version on debian stretch without changing the repos to testing for
> > > the 
> > > whole OS?
> > 
> > I guess that the best you can do is to build your own package from
> > the debian source material.
> 
> 	Alternatively, if the package has been updated in testing you
> can download the .deb and install it manually with 'dpkg -i'.

ABSOLUTELY NOT.

Do not EVER install a package from "testing" on a "stable" release.

If there is a backport of the package, you may use that.

If there is not, you may attempt to backport it yourself.  This may be
easy, difficult, or impossible, depending on the build dependencies of
the package.

If a backport is not feasible, you may build the package manually from
upstream sources and install in /opt or /usr/local.

[toc] | [prev] | [next] | [standalone]


#207315 — Re: Wondering how long it usually takes for a package to move from stable-p-u

FromPierre Fourès <pierre.foures@gmail.com>
Date2019-04-11 16:40 +0200
SubjectRe: Wondering how long it usually takes for a package to move from stable-p-u
Message-ID<xLJ1U-88K-11@gated-at.bofh.it>
In reply to#207308
I didn't saw the question sent twice and answered here.

As answered in [1], I think Luke doesn't need such complicated things
to get his update. To my understanding, just adding
stretch-proposed-updates to /etc/apt/sources.list will solve the
requirement.

[1] https://lists.debian.org/debian-user/2019/04/msg00470.html

Regards,
Pierre

Le jeu. 11 avr. 2019 à 15:02, Greg Wooledge <wooledg@eeg.ccf.org> a écrit :
>
> On Thu, Apr 11, 2019 at 09:51:11AM -0300, Francisco M Neto wrote:
> > On Thu, 2019-04-11 at 08:20 +0400, Jerome BENOIT wrote:
> > > And is there any way I can install just that one package as the
> > > > newer
> > > > version on debian stretch without changing the repos to testing for
> > > > the
> > > > whole OS?
> > >
> > > I guess that the best you can do is to build your own package from
> > > the debian source material.
> >
> >       Alternatively, if the package has been updated in testing you
> > can download the .deb and install it manually with 'dpkg -i'.
>
> ABSOLUTELY NOT.
>
> Do not EVER install a package from "testing" on a "stable" release.
>
> If there is a backport of the package, you may use that.
>
> If there is not, you may attempt to backport it yourself.  This may be
> easy, difficult, or impossible, depending on the build dependencies of
> the package.
>
> If a backport is not feasible, you may build the package manually from
> upstream sources and install in /opt or /usr/local.
>

[toc] | [prev] | [next] | [standalone]


#207320

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2019-04-11 17:20 +0200
Message-ID<xLJEC-b3-3@gated-at.bofh.it>
In reply to#207308
On Thu 11 Apr 2019 at 09:01:37 (-0400), Greg Wooledge wrote:
> On Thu, Apr 11, 2019 at 09:51:11AM -0300, Francisco M Neto wrote:
> > On Thu, 2019-04-11 at 08:20 +0400, Jerome BENOIT wrote:
> > > And is there any way I can install just that one package as the
> > > > newer 
> > > > version on debian stretch without changing the repos to testing for
> > > > the 
> > > > whole OS?
> > > 
> > > I guess that the best you can do is to build your own package from
> > > the debian source material.
> > 
> > 	Alternatively, if the package has been updated in testing you
> > can download the .deb and install it manually with 'dpkg -i'.
> 
> ABSOLUTELY NOT.
> 
> Do not EVER install a package from "testing" on a "stable" release.
> 
> If there is a backport of the package, you may use that.
> 
> If there is not, you may attempt to backport it yourself.  This may be
> easy, difficult, or impossible, depending on the build dependencies of
> the package.
> 
> If a backport is not feasible, you may build the package manually from
> upstream sources and install in /opt or /usr/local.

With the *occasional* exception of dependency-less packages like a
foo-doc package (reading ahead of the game) or a font. For example,
I installed fonts-hack-ttf on all my machines, both wheezy and jessie,
as soon as I saw it mentioned here (by Gene I believe). Not the best
for Unicode glyphs, but wonderful for the eyes.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#207332

FromBrian <ad44@cityscape.co.uk>
Date2019-04-11 19:30 +0200
Message-ID<xLLGp-1nm-3@gated-at.bofh.it>
In reply to#207320
On Thu 11 Apr 2019 at 10:12:05 -0500, David Wright wrote:

> On Thu 11 Apr 2019 at 09:01:37 (-0400), Greg Wooledge wrote:
> > On Thu, Apr 11, 2019 at 09:51:11AM -0300, Francisco M Neto wrote:
> > > On Thu, 2019-04-11 at 08:20 +0400, Jerome BENOIT wrote:
> > > > And is there any way I can install just that one package as the
> > > > > newer 
> > > > > version on debian stretch without changing the repos to testing for
> > > > > the 
> > > > > whole OS?
> > > > 
> > > > I guess that the best you can do is to build your own package from
> > > > the debian source material.
> > > 
> > > 	Alternatively, if the package has been updated in testing you
> > > can download the .deb and install it manually with 'dpkg -i'.
> > 
> > ABSOLUTELY NOT.
> > 
> > Do not EVER install a package from "testing" on a "stable" release.
> > 
> > If there is a backport of the package, you may use that.
> > 
> > If there is not, you may attempt to backport it yourself.  This may be
> > easy, difficult, or impossible, depending on the build dependencies of
> > the package.
> > 
> > If a backport is not feasible, you may build the package manually from
> > upstream sources and install in /opt or /usr/local.
> 
> With the *occasional* exception of dependency-less packages like a
> foo-doc package (reading ahead of the game) or a font. For example,
> I installed fonts-hack-ttf on all my machines, both wheezy and jessie,
> as soon as I saw it mentioned here (by Gene I believe). Not the best
> for Unicode glyphs, but wonderful for the eyes.

I'd extend this latitude a bit further to packages that have
dependencies satisified by stable and which provide something
stable doesn't. For example, libsane-hpaio

-- 
Brian..

[toc] | [prev] | [next] | [standalone]


#207342

FromFrancisco M Neto <fmneto@fmneto.com.br>
Date2019-04-11 22:30 +0200
Message-ID<xLOuC-37X-3@gated-at.bofh.it>
In reply to#207332

[Multipart message — attachments visible in raw view] — view raw

On Thu, 2019-04-11 at 18:22 +0100, Brian wrote:
> > With the *occasional* exception of dependency-less packages like a
> > foo-doc package (reading ahead of the game) or a font. For example,
> > I installed fonts-hack-ttf on all my machines, both wheezy and
> > jessie,
> > as soon as I saw it mentioned here (by Gene I believe). Not the best
> > for Unicode glyphs, but wonderful for the eyes.
> 
> I'd extend this latitude a bit further to packages that have
> dependencies satisified by stable and which provide something
> stable doesn't. For example, libsane-hpaio

	That's what I had in mind. I assumed that ca-certificates-java
would fulfill a requirement like that, but maybe it doesn't. Or maybe
people are a bit edgy and end up taking suggestions in a very bad way...

-- 
[]'s,

Francisco M Neto <fmneto@fmneto.com.br>

GPG: 4096R/D692FBF0

[toc] | [prev] | [next] | [standalone]


#209882

Fromandreimpopescu@gmail.com
Date2019-06-14 10:30 +0200
Message-ID<y8PKW-6To-5@gated-at.bofh.it>
In reply to#207294

[Multipart message — attachments visible in raw view] — view raw

On Jo, 11 apr 19, 08:20:18, Jerome BENOIT wrote:
> Hello,
> 
> On 11/04/2019 05:59, Luke Picciau wrote:
> > I have been tracking this package 
> > https://tracker.debian.org/pkg/ca-certificates-java for about a month 
> > because the package version 20170929~deb9u1 which is in stable has a bug 
> > which is blocking my docker image builds. Version 20170929~deb9u2 should 
> > fix it but the package has been in stable-p-u for a while now. How long 
> > usually does it take for a package to move from stable-p-u to stable?
> 
> You have to bear in mind that currently Debian is terminating a cycle.

stable-proposed-updates is currently just a link to 
stretch-proposed-updates.

When buster is released the link will be changed to point to 
buster-proposed-updates instead, it won't affect the contents of the 
archive.

This is just another way of recommending to always use code-names in 
sources.list, as it avoids surprises on releases.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web