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

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

404 trying to use stretch/backports

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

Contents

  404 trying to use stretch/backports Felix Miata <mrmazda@earthlink.net> - 2018-01-11 08:10 +0100
    Re: 404 trying to use stretch/backports likcoras <likcoras@riseup.net> - 2018-01-11 08:20 +0100
      Re: 404 trying to use stretch/backports Felix Miata <mrmazda@earthlink.net> - 2018-01-11 08:30 +0100
        Re: 404 trying to use stretch/backports deloptes <deloptes@gmail.com> - 2018-01-11 09:10 +0100
    Re: 404 trying to use stretch/backports john doe <johndoe65534@mail.com> - 2018-01-11 10:00 +0100
      Re: 404 trying to use stretch/backports Sven Hoexter <sven@timegate.de> - 2018-01-11 10:20 +0100
        Re: 404 trying to use stretch/backports Felix Miata <mrmazda@earthlink.net> - 2018-01-11 13:40 +0100
          Re: 404 trying to use stretch/backports Sven Hoexter <sven@timegate.de> - 2018-01-11 13:50 +0100
            Re: 404 trying to use stretch/backports Brian <ad44@cityscape.co.uk> - 2018-01-11 14:20 +0100
              Re: 404 trying to use stretch/backports deloptes <deloptes@gmail.com> - 2018-01-11 20:30 +0100
                Re: 404 trying to use stretch/backports bw <bwtnguy@yahoo.com> - 2018-01-11 20:50 +0100
                  Re: 404 trying to use stretch/backports Felix Miata <mrmazda@earthlink.net> - 2018-01-11 22:10 +0100
                    Re: 404 trying to use stretch/backports bw <bwtnguy@yahoo.com> - 2018-01-11 22:20 +0100

#190919 — 404 trying to use stretch/backports

Trying to get a non-broken recent version of mc, the instructions on
https://backports.debian.org/Instructions/ fail[1]. How can I get a non-broken
relatively recent mc package installed, e.g. patched 4.8.19, or 4.8.20? Breakage
was fixed 15 months ago[2].

[1] # apt-get update
...
err:9 http://ftp.debian.org/debian stretch-backports/main i386 Packages
	404  Not Found...

[2]
<https://github.com/MidnightCommander/mc/commit/c1cf7e81b9ab1775afc4275cc1aead8b8fc43c7b>
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [next] | [standalone]

#190920

On 01/11/2018 04:08 PM, Felix Miata wrote:
> ...
> err:9 http://ftp.debian.org/debian stretch-backports/main i386 Packages
> 	404  Not Found...

Try adding a trailing slash to the deb url:

http://ftp.debian.org/debian/
and not
http://ftp.debian.org/debian

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

#190921

likcoras composed on 2018-01-11 16:17 (UTC+0900):

> On 01/11/2018 04:08 PM, Felix Miata wrote:
>> ...
>> err:9 http://ftp.debian.org/debian stretch-backports/main i386 Packages
>> 	404  Not Found...
> 
> Try adding a trailing slash to the deb url:
> 
> http://ftp.debian.org/debian/
> and not
> http://ftp.debian.org/debian

Didn't help. :-(
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

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

#190922

Felix Miata wrote:

> Didn't help. :-(

can you open it in the browser

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

#190924

On 1/11/2018 8:08 AM, Felix Miata wrote:
> Trying to get a non-broken recent version of mc, the instructions on
> https://backports.debian.org/Instructions/ fail[1]. How can I get a non-broken
> relatively recent mc package installed, e.g. patched 4.8.19, or 4.8.20? Breakage
> was fixed 15 months ago[2].
> 
> [1] # apt-get update
> ...
> err:9 http://ftp.debian.org/debian stretch-backports/main i386 Packages
> 	404  Not Found...
> 

What lines do you have in 'sources.list'?

The following URL is working for me:

deb http://ftp.debian.org/debian stretch-backports main

-- 
John Doe

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

#190925

On Thu, Jan 11, 2018 at 09:52:00AM +0100, john doe wrote:
> On 1/11/2018 8:08 AM, Felix Miata wrote:
> > Trying to get a non-broken recent version of mc, the instructions on
> > https://backports.debian.org/Instructions/ fail[1]. How can I get a non-broken
> > relatively recent mc package installed, e.g. patched 4.8.19, or 4.8.20? Breakage
> > was fixed 15 months ago[2].
> What lines do you have in 'sources.list'?
> 
> The following URL is working for me:
> 
> deb http://ftp.debian.org/debian stretch-backports main

Hey guys,
there is no backport of the mc package available, so someone has to backport it
first. There is no automatic backport process running because that's technically
not really possible and that's not how backports are intendet to work.

$ rmadison mc
mc         | 3:4.8.3-10    | oldoldstable       | source, amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc
mc         | 3:4.8.13-3    | oldstable          | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
mc         | 3:4.8.13-3    | oldstable-kfreebsd | source, kfreebsd-amd64, kfreebsd-i386
mc         | 3:4.8.18-1    | stable             | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
mc         | 3:4.8.19-1    | testing            | source, amd64, arm64, armel, armhf, i386, mips, mipsel, ppc64el, s390x
mc         | 3:4.8.19-1    | unstable           | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
mc         | 3:4.8.19-1    | unstable-debug     | source
mc         | 3:4.8.19-1+b1 | testing            | mips64el
mc         | 3:4.8.19-1+b1 | unstable           | mips64el

So 4.8.19 is available in unstable, that would be something someone could backport.


Cheeers,
Sven

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

#190929

Sven Hoexter composed on 2018-01-11 10:08 (UTC+0100):

> On Thu, Jan 11, 2018 at 09:52:00AM +0100, john doe wrote:

>> Felix Miata wrote:

>> > Trying to get a non-broken recent version of mc, the instructions on
>> > https://backports.debian.org/Instructions/ fail[1]. How can I get a non-broken
>> > relatively recent mc package installed, e.g. patched 4.8.19, or 4.8.20? Breakage
>> > was fixed 15 months ago[2].

>> What lines do you have in 'sources.list'?

I had looked at it repeatedly, probably close to 10 times. Only after looking
again after some thread replies did I spot stretch/backports where
stretch-backports belongs. :-p

>> The following URL is working for me:

>> deb http://ftp.debian.org/debian stretch-backports main

> Hey guys,
> there is no backport of the mc package available, so someone has to backport it
> first. There is no automatic backport process running because that's technically
> not really possible and that's not how backports are intendet to work.

> So 4.8.19 is available in unstable, that would be something someone could backport.
   I don't know what the intent is in the existence of:
http://ftp.debian.org/debian/pool/main/m/mc/mc_4.8.19-1_i386.deb &
http://ftp.debian.org/debian/pool/main/m/mc/mc-data_4.8.19-1_all.deb

especially with 4.8.20 having been released in November, but I downloaded
manually and installed 4.8.19 with dpkg, and it works just fine compared to the
broken 4.8.18 that had been installed.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

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

#190930

On Thu, Jan 11, 2018 at 07:35:59AM -0500, Felix Miata wrote:

Hi,

>    I don't know what the intent is in the existence of:
> http://ftp.debian.org/debian/pool/main/m/mc/mc_4.8.19-1_i386.deb &
> http://ftp.debian.org/debian/pool/main/m/mc/mc-data_4.8.19-1_all.deb

Those are the packages available and build on unstable. This is a combined
package pool.


> especially with 4.8.20 having been released in November, but I downloaded
> manually and installed 4.8.19 with dpkg, and it works just fine compared to the
> broken 4.8.18 that had been installed.

Well someone has to update the package for unstable first. Then it can migrate at
some point to testing and then someone could build a backport base on this work.
This does not happen on its own.

Using the package from unstable can work but it can also break at any time due
changes in libraries.

Cheers,
Sven

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

#190932

On Thu 11 Jan 2018 at 13:43:19 +0100, Sven Hoexter wrote:

> On Thu, Jan 11, 2018 at 07:35:59AM -0500, Felix Miata wrote:
> 
> Hi,
> 
> >    I don't know what the intent is in the existence of:
> > http://ftp.debian.org/debian/pool/main/m/mc/mc_4.8.19-1_i386.deb &
> > http://ftp.debian.org/debian/pool/main/m/mc/mc-data_4.8.19-1_all.deb
> 
> Those are the packages available and build on unstable. This is a combined
> package pool.
> 
> 
> > especially with 4.8.20 having been released in November, but I downloaded
> > manually and installed 4.8.19 with dpkg, and it works just fine compared to the
> > broken 4.8.18 that had been installed.
> 
> Well someone has to update the package for unstable first. Then it can migrate at
> some point to testing and then someone could build a backport base on this work.
> This does not happen on its own.
> 
> Using the package from unstable can work but it can also break at any time due
> changes in libraries.

I can see what you are saying about mixing stable and unstable but don't
completely follow it in this case. Only mc and mc-data from unstable are
needed and the libraries on stable are sufficient to produce a working
mc. Are you suggesting these libraries could be subject to future change?

-- 
Brian.

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

#190954

Brian wrote:

> I can see what you are saying about mixing stable and unstable but don't
> completely follow it in this case. Only mc and mc-data from unstable are
> needed and the libraries on stable are sufficient to produce a working
> mc. Are you suggesting these libraries could be subject to future change?

Brian, not future - present changes. You compile the code against higher
version of the library and use it with lower version. If the library was
changed (lower -> higher), the program can break when this part of the code
is executed. This might be true for mc or not, we don't know, but the risk
is there. If OP is lucky there won't be an issue, but there is no
guarantee.

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

#190957

On Thu, 11 Jan 2018, deloptes wrote:

> Brian wrote:
> 
> > I can see what you are saying about mixing stable and unstable but don't
> > completely follow it in this case. Only mc and mc-data from unstable are
> > needed and the libraries on stable are sufficient to produce a working
> > mc. Are you suggesting these libraries could be subject to future change?
> 
> Brian, not future - present changes. You compile the code against higher
> version of the library and use it with lower version. If the library was
> changed (lower -> higher), the program can break when this part of the code
> is executed. This might be true for mc or not, we don't know, but the risk
> is there. If OP is lucky there won't be an issue, but there is no
> guarantee.
> 

I wouldn't install mc from unstable or testing on stretch, BUT I do love 
the program.  I don't consider it broken at all, and over the years it has 
been well-maintained and I appreciate it.  I use it all day every day, so 
maybe the best way to get it backported is to setup a testing system and 
test it and file some bugs.

The maintainer already has that on his radar, so maybe it's possible.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858808

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

#190960

bw composed on 2018-01-11 14:44 (UTC-0500):

> I wouldn't install mc from unstable or testing on stretch, BUT I do love 
> the program.  I don't consider it broken at all,

Running which version(s)?

> and over the years it has 
> been well-maintained and I appreciate it.  I use it all day every day, so

For me it or one of its OFM[1] relatives are indispensable. My systems have
trivial uptime without at least one running. Typically more than one are open.

> maybe the best way to get it backported is to setup a testing system and 
> test it and file some bugs.

> The maintainer already has that on his radar, so maybe it's possible.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858808

I filed that bug 10 months ago, 5 months after the fix was committed upstream.
4.8.14, 4.8.15 and 4.8.16 had bugs that for me were not tolerable. 4.8.17 was
good, but the only versions in http://ftp.debian.org/debian/pool/main/m/mc/ are
4.8.13 (ancient), 4.8.18 (by 858808 broken) and 4.8.19 (officially broken, but
including the fix that was officially included in 4.8.20).

[1] http://www.softpanorama.org/OFM/Paradigm/
https://en.wikipedia.org/wiki/File_manager#Orthodox_file_managers
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

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

#190961

On Thu, 11 Jan 2018, Felix Miata wrote:

> bw composed on 2018-01-11 14:44 (UTC-0500):
> 
> > I wouldn't install mc from unstable or testing on stretch, BUT I do love 
> > the program.  I don't consider it broken at all,
> 
> Running which version(s)?

I only use stable, and also have one jessie installation that I am 
attached to and work on occasionally.  I never saw any problems with mc at 
all, except when they redid the mc.ext and it started using xdg-open for 
everything.  That took me awhile to figure out.

 apt policy mc
mc:
  Installed: 3:4.8.18-1
  Candidate: 3:4.8.18-1
  Version table:
 *** 3:4.8.18-1 500
        500 http://http.us.debian.org/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status

> > The maintainer already has that on his radar, so maybe it's possible.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858808
> 
> I filed that bug 10 months ago, 5 months after the fix was committed upstream.
> 4.8.14, 4.8.15 and 4.8.16 had bugs that for me were not tolerable. 4.8.17 was
> good, but the only versions in http://ftp.debian.org/debian/pool/main/m/mc/ are
> 4.8.13 (ancient), 4.8.18 (by 858808 broken) and 4.8.19 (officially broken, but
> including the fix that was officially included in 4.8.20).
> 

Yeah I'm sorry, but debian maintainers rarely jump thru hoops for anybody.  
They are a pretty careful bunch from what I have seen.  I'm happy with the 
package in stretch, but like I said I think testing newer versions is a 
fine idea, just not sure I could help by running the unstable version 
right now.

TY for getting the ball rolling, hope it works out the way you want.

L8r,
bw

[toc] | [prev] | [standalone]

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

csiph-web