[DNG] Devuan ASCII point release

2019-10-21 Thread . fsmithred via Dng
The Devuan ASCII 2.1 point release has begun. The installer isos,
desktop-live and minimal-live isos are currently available for
download here:
http://files.devuan.org/devuan_ascii/
Other images will be uploaded as they are ready.

- The option to choose openrc is more prominent and no longer requires
an Expert install. You can't miss it.

- If you would like to select an alternate bootloader (lilo) or
exclude non-free firmware, you must select one of the Expert install
options.

- The recommended default mirror is now deb.devuan.org.  If you would
like to use a country code mirror, please check
https://pkgmaster.devuan.org/mirror_list.txt to see if there is one
suitable for your needs.

There is more information in the Release Notes:
http://files.devuan.org/devuan_ascii/Release_notes.txt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-21 Thread Joril via Dng

On 22/10/19 06:00, . fsmithred via Dng wrote:

The Devuan ASCII 2.1 point release has begun. The installer isos,
desktop-live and minimal-live isos are currently available for
download here:
http://files.devuan.org/devuan_ascii/
Other images will be uploaded as they are ready.



Great news! :) Will there be a torrent too?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-22 Thread terryc
On Tue, 22 Oct 2019 08:46:47 +0200
Joril via Dng  wrote:

> On 22/10/19 06:00, . fsmithred via Dng wrote:
> > The Devuan ASCII 2.1 point release has begun. The installer isos,
> > desktop-live and minimal-live isos are currently available for
> > download here:
> > http://files.devuan.org/devuan_ascii/
> > Other images will be uploaded as they are ready.  
> 
> 
> Great news! :) Will there be a torrent too?

Hopefully torrents, plural.
For 2.0 I'm hosting a 
 987Mb AMD64 live iso image,
 2.1Gb image date 2019-03-28 and a humungous
 21.3Gb "devuan ascii"  which says it contains;
  desktop-live
  embedded,
  installer-iso,
  minimal-live and
  virtual.

My 2c is offering each of the above as seperate torrents might better
serve the purpose of maximising distribution and encouraging people to
keep them current by using the minal installation then update/upgrade.

> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-22 Thread hal
On October 21, 2019 11:00:01 PM CDT, ". fsmithred via Dng"  
wrote:
:: The Devuan ASCII 2.1 point release has begun. The installer isos,
:: desktop-live and minimal-live isos are currently available for
:: download here:
:: http://files.devuan.org/devuan_ascii/
:: Other images will be uploaded as they are ready.
:: 
:: - The option to choose openrc is more prominent and no longer
:: requires
:: an Expert install. You can't miss it.
:: 
:: - If you would like to select an alternate bootloader (lilo) or
:: exclude non-free firmware, you must select one of the Expert install
:: options.
:: 
:: - The recommended default mirror is now deb.devuan.org.  If you would
:: like to use a country code mirror, please check
:: https://pkgmaster.devuan.org/mirror_list.txt to see if there is one
:: suitable for your needs.
:: 
:: There is more information in the Release Notes:
:: http://files.devuan.org/devuan_ascii/Release_notes.txt
:: ___
:: Dng mailing list
:: Dng@lists.dyne.org
:: https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Thank you!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-22 Thread golinux

On 2019-10-22 01:46, Joril via Dng wrote:

On 22/10/19 06:00, . fsmithred via Dng wrote:

The Devuan ASCII 2.1 point release has begun. The installer isos,
desktop-live and minimal-live isos are currently available for
download here:
http://files.devuan.org/devuan_ascii/
Other images will be uploaded as they are ready.



Great news! :) Will there be a torrent too?
___



Yes, eventually when someone decides to build it.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-25 Thread Joril via Dng

On 22/10/19 16:11, goli...@devuan.org wrote:

On 2019-10-22 01:46, Joril via Dng wrote:

On 22/10/19 06:00, . fsmithred via Dng wrote:

The Devuan ASCII 2.1 point release has begun. The installer isos,
desktop-live and minimal-live isos are currently available for
download here:
http://files.devuan.org/devuan_ascii/
Other images will be uploaded as they are ready.



Great news! :) Will there be a torrent too?


Downloading & seeding right now :)

Thanks!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-25 Thread Joril via Dng

On 22/10/19 06:00, . fsmithred via Dng wrote:

The Devuan ASCII 2.1 point release has begun. The installer isos,
desktop-live and minimal-live isos are currently available for
download here:
http://files.devuan.org/devuan_ascii/
Other images will be uploaded as they are ready.


For the record I've asked Hetzner to provide the new ISO, since they 
already have Devuan 2.0 it shouldn't be a problem

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-25 Thread Joril via Dng

On 22/10/19 06:00, . fsmithred via Dng wrote:

The Devuan ASCII 2.1 point release has begun. The installer isos,
desktop-live and minimal-live isos are currently available
After installation lsb_release still reports 2.0, should I file a bug 
report?


# uname -r
4.9.0-11-amd64

# lsb_release -a
No LSB modules are available.
Distributor ID: Devuan
Description:Devuan GNU/Linux 2.0 (ascii)
Release:2.0
Codename:   ascii
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-25 Thread fsmithred via Dng

On 10/25/19 9:48 AM, Joril via Dng wrote:

On 22/10/19 06:00, . fsmithred via Dng wrote:

The Devuan ASCII 2.1 point release has begun. The installer isos,
desktop-live and minimal-live isos are currently available

After installation lsb_release still reports 2.0, should I file a bug report?

# uname -r
4.9.0-11-amd64

# lsb_release -a
No LSB modules are available.
Distributor ID:    Devuan
Description:    Devuan GNU/Linux 2.0 (ascii)
Release:    2.0
Codename:    ascii
___



I don't know exactly where the 2.0 is coming from. It's not in 
/etc/os-release, /etc/devuan_version or /etc/issue, and there is no 
/etc/lsb-release file.


man lsb_release says
  "Detection of systems using a mix of packages from various 
distributions or releases is something of a black art; the current 
heuristic tends to assume that the installation is of the earliest 
distribution which is still being used by apt but that heuristic is 
subject to error."


It can't hurt to file a bug report. If you know how to fix it, let us know 
and we can correct that in the future.


fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-25 Thread s
Hello fsmithred,

On Fri, 25 Oct 2019 18:06:06 -0400
fsmithred via Dng  wrote:
> 
> I don't know exactly where the 2.0 is coming from. It's not in 
> /etc/os-release, /etc/devuan_version or /etc/issue, and there is no 
> /etc/lsb-release file.
> 
> man lsb_release says
>"Detection of systems using a mix of packages from various 
> distributions or releases is something of a black art; the current 
> heuristic tends to assume that the installation is of the earliest 
> distribution which is still being used by apt but that heuristic is 
> subject to error."
> 
> It can't hurt to file a bug report. If you know how to fix it, let us know 
> and we can correct that in the future.
> 
> fsmithred

That information come from python2.7 'lsb_release' module..

root@desktop0:~# python2.7 
Python 2.7.13 (default, Sep 26 2018, 18:42:22) 
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import lsb_release
>>> distinfo = lsb_release.get_distro_information()
>>> print(distinfo.get('RELEASE', 'n/a'))
2.0


I will try to trace it, to its origin..

Best Regards,
tux
-- 
tux 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-25 Thread s
Hello fsmithred,
> 
> On Fri, 25 Oct 2019 18:06:06 -0400
> fsmithred via Dng  wrote:
> > 
> > I don't know exactly where the 2.0 is coming from. It's not in 
> > /etc/os-release, /etc/devuan_version or /etc/issue, and there is no 
> > /etc/lsb-release file.
> > 
> > man lsb_release says
> >"Detection of systems using a mix of packages from various 
> > distributions or releases is something of a black art; the current 
> > heuristic tends to assume that the installation is of the earliest 
> > distribution which is still being used by apt but that heuristic is 
> > subject to error."
> > 
> > It can't hurt to file a bug report. If you know how to fix it, let us know 
> > and we can correct that in the future.
> > 
> > fsmithred
> 
> That information come from python2.7 'lsb_release' module..
> 
> root@desktop0:~# python2.7 
> Python 2.7.13 (default, Sep 26 2018, 18:42:22) 
> [GCC 6.3.0 20170516] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import lsb_release
> >>> distinfo = lsb_release.get_distro_information()
> >>> print(distinfo.get('RELEASE', 'n/a'))
> 2.0
> 
> 
> I will try to trace it, to its origin..
> 

I think that I now understand the "black-magic part", also the 
"/etc/lsb-release" :)

in: /usr/lib/python2.7/dist-packages/lsb_release.py
this doesn't help :
 32 RELEASE_CODENAME_LOOKUP = {
 33 '1' : 'jessie',
 34 #'2' : 'ascii',
 35 '2.1' : 'ascii',
 36 # '1.3' : 'bo',
 37 # '2.0' : 'hamm',
 38 # '2.1' : 'slink',
 39 # '2.2' : 'potato',
 40 # '3.0' : 'woody',
 41 # '3.1' : 'sarge',
 42 # '4.0' : 'etch',
 43 # '5.0' : 'lenny',
 44 # '6.0' : 'squeeze',
 45 # '7'   : 'wheezy',
 46 # '8'   : 'jessie',
 47 }

Initial function:
371 def get_distro_information():
372 lsbinfo = get_lsb_information()
373 # OS is only used inside guess_devuan_release anyway
374 for key in ('ID', 'RELEASE', 'CODENAME', 'DESCRIPTION',):
375 if key not in lsbinfo:
376 distinfo = guess_devuan_release()
377 distinfo.update(lsbinfo)
378 return distinfo
379 else:
380 return lsbinfo


I think Its guessed: :)

root@desktop0:~# python2.7
Python 2.7.13 (default, Sep 26 2018, 18:42:22) 
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import lsb_release
>>> distinfo = lsb_release.get_distro_information()
>>> print(distinfo.get('RELEASE', 'n/a'))
2.0
>>> lsb_release.guess_release_from_apt()
{'origin': u'Devuan', 'suite': u'stable', 'version': u'2.0', 'component': 
u'main', 'label': u'Devuan'}


You see here the '2.0' String, and it comes from the funtion 
guess_release_from_apt().. like you can see above..
The guess_release_from_apt() function:
228 def guess_release_from_apt(origin='Devuan', component='main',
229ignoresuites=('experimental'),
230label='Devuan',
231alternate_olabels={'Devuan 
Ports':'packages.devuan.org'}):
232 releases = parse_apt_policy()
233 
234 if not releases:
235 return None
236 
237 # We only care about the specified origin, component, and label
238 releases = [x for x in releases if (
239 x[1].get('origin', '') == origin and
240 x[1].get('component', '') == component and
241 x[1].get('label', '') == label) or (
242 x[1].get('origin', '') in alternate_olabels and
243 x[1].get('label', '') == 
alternate_olabels.get(x[1].get('origin', '')))]
244 
245 # Check again to make sure we didn't wipe out all of the releases
246 if not releases:
247 return None
248 
249 releases.sort(key=lambda tuple: tuple[0],reverse=True)
250 
251 # We've sorted the list by descending priority, so the first entry 
should
252 # be the "main" release in use on the system
253 
254 max_priority = releases[0][0]
255 releases = [x for x in releases if x[0] == max_priority]
256 releases.sort(key=release_index)
257 
258 return releases[0][1]

I am afraid that this info, you already know..
I am not a python guy( I love the Lua simplicity way :) ), I can't help.. :(

Best Regards,
tux

-- 
tux 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-25 Thread Pontus Goffe via Dng

Hi,

On 2019-10-26 02:27, s@po wrote:

You see here the '2.0' String, and it comes from the funtion 
guess_release_from_apt().. like you can see above..
The guess_release_from_apt() function:
 228 def guess_release_from_apt(origin='Devuan', component='main',
 229ignoresuites=('experimental'),
 230label='Devuan',
 231alternate_olabels={'Devuan 
Ports':'packages.devuan.org'}):
 232 releases = parse_apt_policy()
 233
 234 if not releases:
 235 return None
 236
 237 # We only care about the specified origin, component, and label
 238 releases = [x for x in releases if (
 239 x[1].get('origin', '') == origin and
 240 x[1].get('component', '') == component and
 241 x[1].get('label', '') == label) or (
 242 x[1].get('origin', '') in alternate_olabels and
 243 x[1].get('label', '') == 
alternate_olabels.get(x[1].get('origin', '')))]
 244
 245 # Check again to make sure we didn't wipe out all of the releases
 246 if not releases:
 247 return None
 248
 249 releases.sort(key=lambda tuple: tuple[0],reverse=True)
 250
 251 # We've sorted the list by descending priority, so the first entry 
should
 252 # be the "main" release in use on the system
 253
 254 max_priority = releases[0][0]
 255 releases = [x for x in releases if x[0] == max_priority]
 256 releases.sort(key=release_index)
 257
 258 return releases[0][1]

I am afraid that this info, you already know..
I am not a python guy( I love the Lua simplicity way :) ), I can't help.. :(

Best Regards,
tux


Who is a python guy?

parse_apt_policy executes 'apt-cache policy' and parses 
(parse_policy_line) the output for lines beginning with release matching 
o=Devuan and c=main


longnames = {'v' : 'version', 'o': 'origin', 'a': 'suite', 'c' : 
'component', 'l': 'label'}


In my case that is

 500 http://se.deb.devuan.org/merged ascii/main amd64 Packages
 release v=2.0,o=Devuan,a=stable,n=ascii,l=Devuan,c=main,b=amd64
 origin se.deb.devuan.org
//PG

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-26 Thread fsmithred via Dng

On 10/26/19 1:49 AM, Pontus Goffe via Dng wrote:

Hi,

On 2019-10-26 02:27, s@po wrote:
You see here the '2.0' String, and it comes from the funtion 
guess_release_from_apt().. like you can see above..

The guess_release_from_apt() function:
 228 def guess_release_from_apt(origin='Devuan', component='main',
 229    ignoresuites=('experimental'),
 230    label='Devuan',
 231    alternate_olabels={'Devuan 
Ports':'packages.devuan.org'}):

 232 releases = parse_apt_policy()
 233
 234 if not releases:
 235 return None
 236
 237 # We only care about the specified origin, component, and 
label

 238 releases = [x for x in releases if (
 239 x[1].get('origin', '') == origin and
 240 x[1].get('component', '') == component and
 241 x[1].get('label', '') == label) or (
 242 x[1].get('origin', '') in alternate_olabels and
 243 x[1].get('label', '') == 
alternate_olabels.get(x[1].get('origin', '')))]

 244
 245 # Check again to make sure we didn't wipe out all of the 
releases

 246 if not releases:
 247 return None
 248
 249 releases.sort(key=lambda tuple: tuple[0],reverse=True)
 250
 251 # We've sorted the list by descending priority, so the 
first entry should

 252 # be the "main" release in use on the system
 253
 254 max_priority = releases[0][0]
 255 releases = [x for x in releases if x[0] == max_priority]
 256 releases.sort(key=release_index)
 257
 258 return releases[0][1]

I am afraid that this info, you already know..
I am not a python guy( I love the Lua simplicity way :) ), I can't 
help.. :(


Best Regards,
tux


Who is a python guy?

parse_apt_policy executes 'apt-cache policy' and parses 
(parse_policy_line) the output for lines beginning with release matching 
o=Devuan and c=main


longnames = {'v' : 'version', 'o': 'origin', 'a': 'suite', 'c' : 
'component', 'l': 'label'}


In my case that is

  500 http://se.deb.devuan.org/merged ascii/main amd64 Packages
  release v=2.0,o=Devuan,a=stable,n=ascii,l=Devuan,c=main,b=amd64
  origin se.deb.devuan.org
//PG




Where does 'apt-cache policy' get the version number? Oh, maybe it reads 
it from the repo. I see that we have:


pkgmaster.devuan.org/merged/dists/1.0
pkgmaster.devuan.org/merged/dists/2.0
pkgmaster.devuan.org/merged/dists/3.0

and debian has:

debian/dists/Debian8.11
debian/dists/Debian9.11
debian/dists/Debian10.1

Maybe those directory names are supposed to be changed when there's a 
point release.


fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-26 Thread s
Hi Pontus Goffe,

> Hi,
> 
> On 2019-10-26 02:27, s@po wrote:
> > You see here the '2.0' String, and it comes from the funtion 
> > guess_release_from_apt().. like you can see above..
> > The guess_release_from_apt() function:
> >  228 def guess_release_from_apt(origin='Devuan', component='main',
> >  229ignoresuites=('experimental'),
> >  230label='Devuan',
> >  231alternate_olabels={'Devuan 
> > Ports':'packages.devuan.org'}):
> >  232 releases = parse_apt_policy()
> >  233
> >  234 if not releases:
> >  235 return None
> >  236
> >  237 # We only care about the specified origin, component, and label
> >  238 releases = [x for x in releases if (
> >  239 x[1].get('origin', '') == origin and
> >  240 x[1].get('component', '') == component and
> >  241 x[1].get('label', '') == label) or (
> >  242 x[1].get('origin', '') in alternate_olabels and
> >  243 x[1].get('label', '') == 
> > alternate_olabels.get(x[1].get('origin', '')))]
> >  244
> >  245 # Check again to make sure we didn't wipe out all of the 
> > releases
> >  246 if not releases:
> >  247 return None
> >  248
> >  249 releases.sort(key=lambda tuple: tuple[0],reverse=True)
> >  250
> >  251 # We've sorted the list by descending priority, so the first 
> > entry should
> >  252 # be the "main" release in use on the system
> >  253
> >  254 max_priority = releases[0][0]
> >  255 releases = [x for x in releases if x[0] == max_priority]
> >  256 releases.sort(key=release_index)
> >  257
> >  258 return releases[0][1]
> >
> > I am afraid that this info, you already know..
> > I am not a python guy( I love the Lua simplicity way :) ), I can't help.. :(
> >
> > Best Regards,
> > tux
> 
> Who is a python guy?

This LSB scripts were made in python2.7 and adapted for python3( for what it 
seems.. )
I assume they are in pretty much any distro out there..
I agree with fsmithred, they are, some sort of... a "black-magic" art

I don't know who is a "python guy",
I just stated that I am not a Python Programmer, and can't help further :(

Long Story Short:
I stated that I couldn't help, because I am not a Python programmer..
> 
> parse_apt_policy executes 'apt-cache policy' and parses 
> (parse_policy_line) the output for lines beginning with release matching 
> o=Devuan and c=main
> 
> longnames = {'v' : 'version', 'o': 'origin', 'a': 'suite', 'c' : 
> 'component', 'l': 'label'}
> 
> In my case that is
> 
>   500 http://se.deb.devuan.org/merged ascii/main amd64 Packages
>   release v=2.0,o=Devuan,a=stable,n=ascii,l=Devuan,c=main,b=amd64
>   origin se.deb.devuan.org
> //PG
> 

Thanks for clarifying that..
Best Regards,
-- 
tux 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-26 Thread s
Hello fsmithred,

On Sat, 26 Oct 2019 07:51:21 -0400
fsmithred via Dng  wrote:

> On 10/26/19 1:49 AM, Pontus Goffe via Dng wrote:
> > Hi,
> > 
> > On 2019-10-26 02:27, s@po wrote:
> >> You see here the '2.0' String, and it comes from the funtion 
> >> guess_release_from_apt().. like you can see above..
> >> The guess_release_from_apt() function:
> >>  228 def guess_release_from_apt(origin='Devuan', component='main',
> >>  229    ignoresuites=('experimental'),
> >>  230    label='Devuan',
> >>  231    alternate_olabels={'Devuan 
> >> Ports':'packages.devuan.org'}):
> >>  232 releases = parse_apt_policy()
> >>  233
> >>  234 if not releases:
> >>  235 return None
> >>  236
> >>  237 # We only care about the specified origin, component, and 
> >> label
> >>  238 releases = [x for x in releases if (
> >>  239 x[1].get('origin', '') == origin and
> >>  240 x[1].get('component', '') == component and
> >>  241 x[1].get('label', '') == label) or (
> >>  242 x[1].get('origin', '') in alternate_olabels and
> >>  243 x[1].get('label', '') == 
> >> alternate_olabels.get(x[1].get('origin', '')))]
> >>  244
> >>  245 # Check again to make sure we didn't wipe out all of the 
> >> releases
> >>  246 if not releases:
> >>  247 return None
> >>  248
> >>  249 releases.sort(key=lambda tuple: tuple[0],reverse=True)
> >>  250
> >>  251 # We've sorted the list by descending priority, so the 
> >> first entry should
> >>  252 # be the "main" release in use on the system
> >>  253
> >>  254 max_priority = releases[0][0]
> >>  255 releases = [x for x in releases if x[0] == max_priority]
> >>  256 releases.sort(key=release_index)
> >>  257
> >>  258 return releases[0][1]
> >>
> >> I am afraid that this info, you already know..
> >> I am not a python guy( I love the Lua simplicity way :) ), I can't 
> >> help.. :(
> >>
> >> Best Regards,
> >> tux
> > 
> > Who is a python guy?
> > 
> > parse_apt_policy executes 'apt-cache policy' and parses 
> > (parse_policy_line) the output for lines beginning with release matching 
> > o=Devuan and c=main
> > 
> > longnames = {'v' : 'version', 'o': 'origin', 'a': 'suite', 'c' : 
> > 'component', 'l': 'label'}
> > 
> > In my case that is
> > 
> >   500 http://se.deb.devuan.org/merged ascii/main amd64 Packages
> >   release v=2.0,o=Devuan,a=stable,n=ascii,l=Devuan,c=main,b=amd64
> >   origin se.deb.devuan.org
> > //PG
> > 
> 
> 
> Where does 'apt-cache policy' get the version number? Oh, maybe it reads 
> it from the repo. I see that we have:
> 
> pkgmaster.devuan.org/merged/dists/1.0
> pkgmaster.devuan.org/merged/dists/2.0
> pkgmaster.devuan.org/merged/dists/3.0
> 
> and debian has:
> 
> debian/dists/Debian8.11
> debian/dists/Debian9.11
> debian/dists/Debian10.1
> 
> Maybe those directory names are supposed to be changed when there's a 
> point release.
> 

It could be..
Another place, I searched for and makes sense to me:
http://pkgmaster.devuan.org/merged/dists/ascii/Release

Best Regards,
-- 
tux 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-26 Thread s
Hello,

On Sat, 26 Oct 2019 14:32:55 +0100
s@po  wrote:

> Hello fsmithred,
> 
> On Sat, 26 Oct 2019 07:51:21 -0400
> fsmithred via Dng  wrote:
> 
> > On 10/26/19 1:49 AM, Pontus Goffe via Dng wrote:
> > > Hi,
> > > 
> > > On 2019-10-26 02:27, s@po wrote:
> > >> You see here the '2.0' String, and it comes from the funtion 
> > >> guess_release_from_apt().. like you can see above..
> > >> The guess_release_from_apt() function:
> > >>  228 def guess_release_from_apt(origin='Devuan', component='main',
> > >>  229    ignoresuites=('experimental'),
> > >>  230    label='Devuan',
> > >>  231    alternate_olabels={'Devuan 
> > >> Ports':'packages.devuan.org'}):
> > >>  232 releases = parse_apt_policy()
> > >>  233
> > >>  234 if not releases:
> > >>  235 return None
> > >>  236
> > >>  237 # We only care about the specified origin, component, and 
> > >> label
> > >>  238 releases = [x for x in releases if (
> > >>  239 x[1].get('origin', '') == origin and
> > >>  240 x[1].get('component', '') == component and
> > >>  241 x[1].get('label', '') == label) or (
> > >>  242 x[1].get('origin', '') in alternate_olabels and
> > >>  243 x[1].get('label', '') == 
> > >> alternate_olabels.get(x[1].get('origin', '')))]
> > >>  244
> > >>  245 # Check again to make sure we didn't wipe out all of the 
> > >> releases
> > >>  246 if not releases:
> > >>  247 return None
> > >>  248
> > >>  249 releases.sort(key=lambda tuple: tuple[0],reverse=True)
> > >>  250
> > >>  251 # We've sorted the list by descending priority, so the 
> > >> first entry should
> > >>  252 # be the "main" release in use on the system
> > >>  253
> > >>  254 max_priority = releases[0][0]
> > >>  255 releases = [x for x in releases if x[0] == max_priority]
> > >>  256 releases.sort(key=release_index)
> > >>  257
> > >>  258 return releases[0][1]
> > >>
> > >> I am afraid that this info, you already know..
> > >> I am not a python guy( I love the Lua simplicity way :) ), I can't 
> > >> help.. :(
> > >>
> > >> Best Regards,
> > >> tux
> > > 
> > > Who is a python guy?
> > > 
> > > parse_apt_policy executes 'apt-cache policy' and parses 
> > > (parse_policy_line) the output for lines beginning with release matching 
> > > o=Devuan and c=main
> > > 
> > > longnames = {'v' : 'version', 'o': 'origin', 'a': 'suite', 'c' : 
> > > 'component', 'l': 'label'}
> > > 
> > > In my case that is
> > > 
> > >   500 http://se.deb.devuan.org/merged ascii/main amd64 Packages
> > >   release v=2.0,o=Devuan,a=stable,n=ascii,l=Devuan,c=main,b=amd64
> > >   origin se.deb.devuan.org
> > > //PG
> > > 
> > 
> > 
> > Where does 'apt-cache policy' get the version number? Oh, maybe it reads 
> > it from the repo. I see that we have:
> > 
> > pkgmaster.devuan.org/merged/dists/1.0
> > pkgmaster.devuan.org/merged/dists/2.0
> > pkgmaster.devuan.org/merged/dists/3.0
> > 
> > and debian has:
> > 
> > debian/dists/Debian8.11
> > debian/dists/Debian9.11
> > debian/dists/Debian10.1
> > 
> > Maybe those directory names are supposed to be changed when there's a 
> > point release.
> > 
> 
> It could be..
> Another place, I searched for and makes sense to me:
> http://pkgmaster.devuan.org/merged/dists/ascii/Release
> 
After some digging I believe it comes from:
root@desktop0:~# apt-cache policy lsb-release
lsb-release:
  Installed: 4.1+devuan2
  Candidate: 4.1+devuan2
  Version table:
 *** 4.1+devuan2 500
500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
100 /var/lib/dpkg/status
root@desktop0:~# apt-cache policy
Package files:
 100 /var/lib/dpkg/status
 release a=now
 100 http://pkgmaster.devuan.org/merged ascii-backports/main amd64 Packages
 release v=2.0.0,o=Devuan 
Backports,a=stable-backports,n=ascii-backports,l=Devuan Backports,c=main,b=amd64
 origin pkgmaster.devuan.org
 500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
 release v=2.0,o=Devuan,a=stable,n=ascii,l=Devuan,c=main,b=amd64
 origin pkgmaster.devuan.org

So I think it comes from :
root@desktop0:~# wget -qO- 
http://pkgmaster.devuan.org/merged/dists/{ascii,ascii-backports,ascii-security,ascii-updates}/Release|grep
 Version --color
Version: 2.0
Version: 2.0.0
Version: 2.0
Version: 2.0.0

Best Regards,
-- 
tux 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-26 Thread fsmithred via Dng

On 10/26/19 9:54 AM, s@po wrote:




Where does 'apt-cache policy' get the version number? Oh, maybe it reads
it from the repo. I see that we have:



It could be..
Another place, I searched for and makes sense to me:
http://pkgmaster.devuan.org/merged/dists/ascii/Release




So I think it comes from :
root@desktop0:~# wget -qO- 
http://pkgmaster.devuan.org/merged/dists/{ascii,ascii-backports,ascii-security,ascii-updates}/Release|grep
 Version --color
Version: 2.0
Version: 2.0.0
Version: 2.0
Version: 2.0.0

Best Regards,



Yes, thank you. I got confirmation from another source that it's in the 
Release file. I'll find someone to make the changes.


fsmithred



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan ASCII point release

2019-10-26 Thread s
Hello,

On Sat, 26 Oct 2019 11:03:11 -0400
fsmithred  wrote:

> On 10/26/19 9:54 AM, s@po wrote:
>
> >>> Where does 'apt-cache policy' get the version number? Oh, maybe it reads
> >>> it from the repo. I see that we have:
> 
> >> It could be..
> >> Another place, I searched for and makes sense to me:
> >> http://pkgmaster.devuan.org/merged/dists/ascii/Release
> >>
> 
> > So I think it comes from :
> > root@desktop0:~# wget -qO- 
> > http://pkgmaster.devuan.org/merged/dists/{ascii,ascii-backports,ascii-security,ascii-updates}/Release|grep
> >  Version --color
> > Version: 2.0
> > Version: 2.0.0
> > Version: 2.0
> > Version: 2.0.0
> > 
> > Best Regards,
> > 
> 
> Yes, thank you. I got confirmation from another source that it's in the 
> Release file. I'll find someone to make the changes.
> 

You welcome,
I also want to take the oportunity to thank you, for the work you have been 
doing! :)

Best Regards,
-- 
tux 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng