molior-dbs/molior

Molior - Debian Build System

molior's Issues

Support building udeb packages

allow to build i.e. systemd

UnboundLocalError in mirror API

Oct 08 09:44:57 molior-test molior[50645]: local variable 'state' referenced before assignment
                                           Traceback (most recent call last):
                                             File "/usr/lib/python3/dist-packages/molior/molior/worker_aptly.py", line 242, in finalize_mirror
                                               upd_progress = await aptly.mirror_get_progress(task_id)
                                             File "/usr/lib/python3/dist-packages/molior/aptly/api.py", line 399, in mirror_get_progress
                                               state.update(progress)
                                           UnboundLocalError: local variable 'state' referenced before assignment

Delete package from aptly

Add a functionality where a package (build) can be deleted and also the package will be deleted from the aptly repo server.

Consider adding audit tables

To track all changes to tables, like inserts, updates, deletions, etc.

Add a reason why a build failed

At the moment, we just mark the build as "build_failed". It would be useful to know why the build failed, e.g. an error code or error message, so clients can decide to retrigger the build on certain errors.

Manually triggerring a clone of a repo in "error" state throws JS error

This is the error:

main-es2015.c758c30ab342f47543ec.js:1 ERROR TypeError: Cannot read property 'unsubscribe' of undefined
    at RS.ngOnDestroy (main-es2015.c758c30ab342f47543ec.js:1)
    at _i (main-es2015.c758c30ab342f47543ec.js:1)
    at gi (main-es2015.c758c30ab342f47543ec.js:1)
    at fi (main-es2015.c758c30ab342f47543ec.js:1)
    at bo (main-es2015.c758c30ab342f47543ec.js:1)
    at Co (main-es2015.c758c30ab342f47543ec.js:1)
    at yo (main-es2015.c758c30ab342f47543ec.js:1)
    at bo (main-es2015.c758c30ab342f47543ec.js:1)
    at Co (main-es2015.c758c30ab342f47543ec.js:1)
    at wo (main-es2015.c758c30ab342f47543ec.js:1)

Improve logging by showing logged in user that triggers an API

When debugging, it's useful to know which API calls are triggered manually by logged in users.

Please replace "reproducible" with "repeatable"

As I understand it, Molior provides specific Debian versions of packages to ensure that things do not change "underneath" you. However, this is not what is meant by the term "reproducible" in 2019.

I suggest, at least for now, that you change the nouns to "repeatable" to avoid further confusion.

Too many open files errors

Molior logs show these errors:

May 03 03:57:42 molior-prod molior[18481]: socket.accept() out of system resource
                                           socket: <socket.socket fd=11, family=AddressFamily.AF_INET, type=SocketKind
                                           Traceback (most recent call last):
                                             File "/usr/lib/python3.7/asyncio/selector_events.py", line 156, in _accep
                                             File "/usr/lib/python3.7/socket.py", line 212, in accept
                                           OSError: [Errno 24] Too many open files

lsof shows a lot of lines like:

python3 7669 molior 3075w      REG               0,46     2319 4052384115 /var/lib/molior/buildout/147209/build.log (rkansw05-svm05e.kau.roche.com:/molior/molior-data)
python3 7669 molior 3076w      REG               0,46     2629 4051705434 /var/lib/molior/buildout/147193/build.log (rkansw05-svm05e.kau.roche.com:/molior/molior-data)
python3 7669 molior 3077w      REG               0,46     2432 4055518686 /var/lib/molior/buildout/147239/build.log (rkansw05-svm05e.kau.roche.com:/molior/molior-data)
python3 7669 molior 3078w      REG               0,46     2462 4051863571 /var/lib/molior/buildout/147221/build.log (rkansw05-svm05e.kau.roche.com:/molior/molior-data)
python3 7669 molior 3079w      REG               0,46     2331 4052057892 /var/lib/molior/buildout/147207/build.log (rkansw05-svm05e.kau.roche.com:/molior/molior-data)
python3 7669 molior 3080w      REG               0,46     2360 4051851157 /var/lib/molior/buildout/147237/build.log (rkansw05-svm05e.kau.roche.com:/molior/molior-data)
python3 7669 molior 3081w      REG               0,46    38084 4055655080 /var/lib/molior/buildout/147190/build.log (rkansw05-svm05e.kau.roche.com:/molior/molior-data)

suggesting that "build.log" files are not closed properly.

Add ability to take snapshots

Add a functionality where a user can create a snapshot of an projectversion and this will then be added a s a new (locked) projectversion.

Can't login latest molior 1.4: POST /api/login 404 Not Found

Steps:

• Follows this guide to install Molior on Ubuntu svr 20: https://github.com/molior-dbs/molior/blob/master/INSTALL.md
• Login using admin / molior-dev as defined in /etc/molior/molior.yml:
  
• Return error: /api/login 404 Not Found
  

Did I miss anything?

[Question] about mirroring non-base repositories

Is it possible to mirror a 3rd party repo, lets say for rabbitmq, but without selecting 'base mirror'?
The thing is I would like to mirror only few gigs instead of 100 gigs (whole distro)

I understand this is probably because of dependencies, but is there a way around it? And if.so, is it safe? I mostly lived in rpm world until now, when in comes to repos and repo mirroring.

Improve mirroring multiple components

The components like main, controb, non-free should be separate repositories, currently they are merged.

PGP key mismatch

Attempting to follow the INSTALL.md, however, the signature on the repo does not match the public key retrieved.

[Feature Request] Dockerized setup with docker-compose file

question: multiple components with aptly

Do you support mirrors with multiple components? If so, how do you do it with aptly? How does the aptly single-component convention affect molior?

https://www.aptly.info/doc/feature/multi-component/