This fragment is somewhat intelligible.  Documentation is important.  We all know that.  It also needs to be written.  It doesn't write itself.  As to where is the right place?  Well, that depends . . .

well i can made, but where? spell check can made by others.. and dont said "hard to track your write", documentation its missing and are need!

does users can go here and ask for problems? and then when ask call babyes and other .. so then i still waithing for all the reported bugs, i have problems to track repositories (well at least that was rsync lack of)

i noted that Devuan said in the main page that its a dristribution not copy of debian, but i also read in some where here and in git.debuan that 90% are DIRECTLY copy of debian...

in that case why not copy the debian documentation in a system wiki and then users can made changes over the copy.. if devuan its just a copy without the sytemd, only we must change the systemd related and done!

its a obvious choice and the more inteligent way! please! event pretent to do something that have many lacks

again its debuan for the users or for "dev"'s only?

If you don't know the answer by now, you're not paying attention so I'm not going to repeat myself.

This fragment is somewhat intelligible.  Documentation is important.  We all know that.  It also needs to be written.  It doesn't write itself.  As to where is the right place?  Well, that depends . . .

I have no idea what you're trying to say here but I do know that you end by again wrongly judging and and insulting those of us working so hard on a project that you bitch about in nearly every post.  Some gratitude for the tremendous effort it's taken to get this far would be appropriate.  But then finding anything positive or remotely helpful in one of your posts is the last thing I'd ever expect.  If you don't like it here and have such a low estimation of our efforts, please move on elsewhere . . .

golinux wrote:

Since the devs don't have time to babysit this forum,

Babysit?
Someday I will come up with an answer to that and it will be with a noteworthy interest rate!
:-P

The "Codename:" problem still is unanswered.
Trying to debmirror a dist with wrong codename results in mirroring the dist matching that codename...
That can't be correct!

again its debuan for the users or for "dev"'s only?

if documentation were put in right place, "babysit"'s dont ask so many to the "dev"'s ok, more respect to the users AGAIN!

golinux wrote:

yeti wrote:

The "Codename:" problem still is unanswered.
Trying to debmirror a dist with wrong codename results in mirroring the dist matching that codename...
That can't be correct!

Have you filed a bug report?  Or tried to contact a dev on #devuan or #devuan-dev?

Did the "or" part...

Yeah saw it in the backlog and just now connected it to you.     I can't remember if it was actually solved. (Too much to remember . . .)  A bug report is a more permanent way of recording it.  irc logs quickly fade into oblivion.

In summary: infrastructure followed by amprolla3.

yeti wrote:

The "Codename:" problem still is unanswered.
Trying to debmirror a dist with wrong codename results in mirroring the dist matching that codename...
That can't be correct!

Have you filed a bug report?  Or tried to contact a dev on #devuan or #devuan-dev?

Did the "or" part...

golinux wrote:

Since the devs don't have time to babysit this forum,

Babysit?
Someday I will come up with an answer to that and it will be with a noteworthy interest rate!
:-P

LOL!  Looking forward to something 'noteworthy'!!

Have you filed a bug report?  Or tried to contact a dev on #devuan or #devuan-dev?  It is unlikely anyone who could fix this would see it here.

Since the devs don't have time to babysit this forum,

Babysit?
Someday I will come up with an answer to that and it will be with a noteworthy interest rate!
:-P

The "Codename:" problem still is unanswered.
Trying to debmirror a dist with wrong codename results in mirroring the dist matching that codename...
That can't be correct!

You might want to read more about amprolla.  It's just a search away if you would care to try:

https://git.devuan.org/devuan-infrastructure/amprolla

https://talk.devuan.org/t/amprolla-pack … -proxy/298

https://github.com/parazyd/amprolla

auto mirror its a main  entry to proxy' the packages for users in a automatic way.. umm maybe amprola must be the reason ?

(yeti@kumari:13)/wrk/mirrors$ ./devuan.sh 
Mirroring to /wrk/mirrors/devuan from http://auto.mirror.devuan.org/merged/
Arches: arm64
Dists: ascii,ascii-backports,ascii-security
Sections: main,contrib,non-free
Pdiff mode: use
Not checking Release gpg signatures.
Will clean up after mirroring.
Attempting to get lock ...
Updating remote trace files (using rsync) ...
rsync: failed to connect to auto.mirror.devuan.org (2001:41d0:8:2c55::a2): Connection refused (111)
rsync: failed to connect to auto.mirror.devuan.org (46.105.191.77): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(128) [Receiver=3.1.1]
Warning: failed to use rsync to download extra files.
Getting meta files ...
[  0%] Getting: dists/ascii/Release...   #** GET http://auto.mirror.devuan.org/merged/dists/ascii/Release ==> 200 OK
ok
[  0%] Getting: dists/ascii/Release.gpg...       #** GET http://auto.mirror.devuan.org/merged/dists/ascii/Release.gpg ==> 200 OK
ok
[  0%] Getting: dists/ascii-backports/Release...         #** GET http://auto.mirror.devuan.org/merged/dists/ascii-backports/Release ==> 200 OK
ok
[  0%] Getting: dists/ascii-backports/Release.gpg...     #** GET http://auto.mirror.devuan.org/merged/dists/ascii-backports/Release.gpg ==> 200 OK (1s)
ok
Duplicate dist ascii.
WARNING: releasing 1 pending lock...

`http://ftp.debian.org/debian/dists/stretch-backports/Release`:

Origin: Debian Backports
Label: Debian Backports
Suite: stretch-backports
Codename: stretch-backports
Date: Wed, 26 Jul 2017 02:29:47 UTC
Valid-Until: Wed, 02 Aug 2017 02:29:47 UTC
NotAutomatic: yes
ButAutomaticUpgrades: yes
Acquire-By-Hash: yes
Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
Components: main contrib non-free
Description: Backports for the Stretch distribution
MD5Sum:
 d41d8cd98f00b204e9800998ecf8427e        0 contrib/Contents-amd64

`http://auto.mirror.devuan.org/merged/dists/ascii-backports/Release`:

Origin: Devuan
Label: ascii-backports
Suite: ascii-backports
Version: 2.0.0
Codename: ascii
Date: Tue, 25 Jul 2017 20:31:36 UTC
Valid-Until: Tue, 01 Aug 2017 20:31:36 UTC
NotAutomatic: yes
ButAutomaticUpgrades: yes
Architectures: alpha amd64 arm64 armel armhf hppa i386 ia64 mips mipsel powerpc ppc64el s390x sparc
Components: main contrib non-freeMD5Sum:
  8a4b59cb71d78f27c2cd19431cccd2f8      808 non-free/binary-amd64/Packages.xz

There's a linefeed missing between `non-free` and `MD5Sum:` and the field `Codename:` probably should be `ascii-backports` (same for `ascii-proposed-updates` and `ascii-updates`).

Apart from these showstoppers for mirroring `ascii-backports`, `ascii-proposed-updates` and `ascii-updates` the remaining results look ok so far:

(yeti@kumari:13)/wrk/mirrors$ du -sh devuan/*/*
16M     devuan/dists/ascii
180K    devuan/dists/ascii-security
0       devuan/dists/testing
0       devuan/dists/testing-security
56G     devuan/pool/DEBIAN
20M     devuan/pool/DEVUAN
8,0K    devuan/project/trace

Currently I have no ASCII/arm64⁽¹⁾ system, so I cannot test installing from this mirror.

(1): Last weekend I reinstalled all my Devuan-PIs with Jessie because...
...eeeehhh... ***cough³*** <whisper> ASCII </whisper>

——————————

Edit@20170726-1042-UTC: Bonus question.

What's the difference between `auto.mirror.devuan.org` and `packages.devuan.org`?

——————————

Edit@20170726-1054-UTC: Jessie has the same `Codename:` problems.

E.g.: .../jessie-proposed-updates/Release

with debmirro using debian : "too many redirects"

When?
Directly after starting or after running some time?
Here (currently on Debian/Jessie) it is slowly doing it's task but I never had the patience to test it more than half an hour or so and sure that is far away from completing...

Currently I have no Devuan system with enough free harddisk space to test it there...

with debmirror using Devuan: 404 not found