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]
Hi,
You will have to wait for the next point release of Stretch for this
package being integrated in the stable repository. Meanwhile, you can
add the proposed-update repository to your sources.list to grab the
proposed-updates, like described in [1]. Also, looking at [2], we see
Le jeu. 11 avr. 2019 à 02:52, David Christensen
a écrit :
>
> On 4/10/19 1:32 AM, Pierre Fourès wrote:
> > Le ven. 5 avr. 2019 à 22:08, David Christensen
> > a écrit :
> >>
> >> AFAIK dm-crypt is the canonical disc encryption technology on Linux (see
> >
Le ven. 5 avr. 2019 à 17:07, Pierre Fourès a écrit :
> I would like a « simple and easy » solution.
In the hope it may help someone or at least give some food for
thoughts, here is what I eventually did to fix my issue.
I use apt-cacher-ng. I first thought to log in the instance and g
Le ven. 5 avr. 2019 à 22:08, David Christensen
a écrit :
>
> AFAIK dm-crypt is the canonical disc encryption technology on Linux (see
> crypttab(5) and cryptsetup(8)). I like the fact that it operates at the
> device level, so everything on an encrypted disc or partition is
> automatically and
Hi,
I'm in the process of rebuilding new virtual instances for the Desktop
user's of my company. We provides these instance in order to be able
to run the validated software stack on non-validated software stacks
(ie. running a virtual box inside a custom installed Linux, or on OSX
or Windows).
You maybe duplicated it, or added it in the sources.list.d/ directory ?
You could run the following command to list out all active references
in your current configuration.
grep -R "deb " /etc/apt/sources.list*
Cheers,
Pierre.
Le jeu. 4 avr. 2019 à 10:50, john doe a écrit :
>
> On 4/4/2019
Hello,
I have been wondering about the same question in the latest days and
here is some of the gathering.
The jessie-backports are deprecated since July 2018 as stated in this
message [1]. They are not part of the LTS, as stated in [2] in section
« Deprecation of LTS support for backports ».
Le mar. 26 mars 2019 à 13:45, Pierre Fourès a écrit :
>
> My current /etc/apt/sources.list looks like this :
> > deb http://http.debian.net/debian jessie main
> > deb http://security.debian.org/ jessie/updates main
> > deb http://archive.debian.org/debian jessie-backpo
Le jeu. 28 mars 2019 à 11:32, a écrit :
>
> If you find that interesting...
>
> imagine you're running your emacs (as a server) and want to
> [...]
>
> Bam :-)
>
> So there are many nifty things in Emacs. But the real killer
> is the integration of all those nifty things.
>
Wow, this gave me the
> https://lists.debian.org/debian-backports/2019/03/msg00043.html
>
> Confirms the Jessie backports archive. I have just dropped it from the
> sources.list
Thanks Bernie for your feedback.
It seems we've fallen into the same confusion due to both the
backports repository being moved to the
Le mar. 26 mars 2019 à 16:21, Curt a écrit :
>
> https://backports.debian.org/
>
> > Backports are packages taken from the next Debian release (called
> > "testing"),
> > adjusted and recompiled for usage on Debian stable.
>
> From that I infer that jessie-backports are like woolly mammoths.
Le mar. 26 mars 2019 à 14:20, Nicholas Geovanis
a écrit :
> I'm pretty sure that I encountered this in the past but I don't have any
> proof to hand.
> IIRC when the release enters LTS the backports stop being augmented. Is that
> (still)
> correct? Therefore there will be no repository for
Yauhen's mail seems not to find its way towards debian-user@, so he
asked me to foward it. Here it is :
Le mar. 26 mars 2019 à 12:11, Yauhen Shulitski a écrit :
>
> The following repositories work for me:
>
> deb http://deb.debian.org/debian/ jessie main contrib non-free
> deb-src
As mentioned in [1], I'm experiencing something similar. The
jessie-updates/ repository just seems to be gone due to the archival
process of Jessie [2].
I'm currently wondering if it has any impacts, ie, is it now
reintegrated in the main archived repository. But seeing your outputs
seems to
in all this possibilities.
Pierre.
Le mar. 26 mars 2019 à 13:31, Roberto C. Sánchez a écrit :
>
> On Tue, Mar 26, 2019 at 12:26:04PM -, Curt wrote:
> > On 2019-03-26, Pierre Fourès wrote:
> >
> > > W: Failed to fetch
> > > http://archive.debian.ne
c/apt/sources.list looks like this :
> deb http://http.debian.net/debian jessie main
> deb http://security.debian.org/ jessie/updates main
> deb http://archive.debian.org/debian jessie-backports main
Pierre.
[1] : http://archive.debian.org/debian/README
Le mar. 26 mars 2019 à 13:26, Cur
As mentioned in [1], I'm experiencing the same problem. The
jessie-updates/ repository just seems to be gone due to the archival
process of Jessie. I'm currently wondering if it's now integrated in
the main repository, or if it is elsewhere, or just gone.
Regards,
Pierre.
[1] :
?
[1] : https://wiki.debian.org/LTS/Using?action=diff=40=39
Pierre.
Le mar. 26 mars 2019 à 11:06, Curt a écrit :
>
> On 2019-03-26, Pierre Fourès wrote:
> > This is precisely what my problem is about. This is why I wondered
> > where jessie-updates/ went, or if https://wiki.de
In the meantime of understanding what's happening with jessie-updates,
I removed the jessie-updates/ references in order to dig a little more
as I also require jessie-backports (which isn't anymore in the
mirrors, but is in the archive).
For the context, I have a multi-step process installing
es
> used instead.
Le mar. 26 mars 2019 à 10:00, Curt a écrit :
>
> On 2019-03-26, Pierre Fourès wrote:
> > Hi,
> >
> > I just stumbled upon the fact that Jessie and Wheezy was removed from
> > the mirrors, except for the LTS. (cf.
> > https://lists.debian.
Hi,
I just stumbled upon the fact that Jessie and Wheezy was removed from
the mirrors, except for the LTS. (cf.
https://lists.debian.org/debian-devel-announce/2019/03/msg6.html).
I still currently use Jessie and my automated install build just broke
this morning. I only use i386 and amd64, so
22 matches
Mail list logo
