Amprolla3 is out for testing

fsmithred · 2017-10-20 21:57:56

Dear dev1rs,

We are happy to announce that 'amprolla3', the rewrite of nextime's
amprolla by parazyd and Wizzup, is finally up and running and ready
to be tested.

The code can be found at:

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

The rewrite increases the frequency of merges (now performed
every few minutes, rather than once a day), meaning that new packages,
updates, and upgrades will be available almost immediately to Devuan
users.

We have set up a second host which will serve Devuan packages as
merged by the new amprolla3. It is now available at
pkgmaster.devuan.org and currently serves Devuan Jessie, Devuan Ascii,
and Devuan Ceres, including all the *-security and *-updates sections.
The host, pkgmaster.devuan.org, also supports https.

If you want to help testing the new amprolla3, you just need to:

- replace "auto.mirror.devuan.org" with "pkgmaster.devuan.org" in
your /etc/apt/sources.list

- # apt-get update
- # apt-get install devuan-keyring

Then just use it as you did with auto.mirror.devuan.org. Please
report any bugs on https://bugs.devuan.org, as usual.

The current auto.mirror.devuan.org host remains up and running and
perfectly usable. Once the testing of amprolla3 is complete, the
transition to the new system should be seamless and transparent to all
users.

The new amprolla3 also provides support for the currently missing
Contents*.gz files (solving the apt-file bug). The feature will be
made available in the coming couple of days.

The Dev1Devs

**edit by golinux**
Please see the "amprolla magic" thread for an in-depth understanding of what amprolla does.

sgage · 2017-10-21 02:16:32

This is good stuff! Getting this infrastructure sorted out is really important... good work!

fungus · 2017-10-21 06:39:25

In Arch there is pkg manager like synaptic called pamac. There is a tray-app-indicator for pamac that changes the color of a star when an upgadeable pkg is available. One can set the period when repeated updates take place.
But wouldn't the frequency you mention above take a toll on the mirrors?

fsmithred · 2017-10-21 10:07:40

I expect that mirrors can set their own refresh rate. Most times they check, there won't be any changes, so nothing to do.

Dyslectics Untie! It's pacman. Debian/Devuan has update-notifier in jessie. The name has been changed to gnome-packagekit in stretch, and you can't have it because of the chain of deps. There is a way to have conky show the number of updates available. (Search dng archives or ask me nicely and I'll figure out what I did.)

garyz.dev1 · 2017-10-21 14:44:26

I changed to pkgmaster.devuan.org

list my sources.list
#deb http://us.mirror.devuan.org/merged/ jessie main
deb http://pkgmaster.devuan.org/merged/ jessie main <---
#deb-src http://us.mirror.devuan.org/merged/ jessie main
# jessie-security, previously known as 'volatile'
#deb http://us.mirror.devuan.org/merged/ jessie-security main non-free
deb http://pkgmaster.devuan.org/merged/ jessie-security main non-free <---
#deb http://us.mirror.devuan.org/merged/ jessie-security main
#deb-src http://us.mirror.devuan.org/merged/ jessie-security main non-free
# jessie-updates, previously known as 'volatile'
#deb http://us.mirror.devuan.org/merged/ jessie-updates main non-free
deb http://pkgmaster.devuan.org/merged/ jessie-updates main non-free <---
#deb-src http://us.mirror.devuan.org/merged/ jessie-updates main non-free
#deb http://packages.devuan.org/devuan/ experimental main
#deb http://download.virtualbox.org/virtualbox/debian jessie contrib
olzeke51@devuan:~$

and got these three updates: my last update was 10-13

olzeke51@devuan:/$ apt list --upgradable
Listing... Done
wpasupplicant/stable-security 2.3-1+deb8u5 amd64 [upgradable from: 2.3-1+deb8u4]
xserver-common/stable-security 2:1.16.4-1+deb8u2 all [upgradable from: 2:1.16.4-1+deb8u1]
xserver-xorg-core/stable-security 2:1.16.4-1+deb8u2 amd64 [upgradable from: 2:1.16.4-1+deb8u1+b1]

but I didn't do the devuan-keyring install per
https://dev1galaxy.org/viewtopic.php?id=1671

so I tried to install it and got this -- [last keyring updated on 10-13!!-my last update]

olzeke51@devuan:~$ sudo apt-get install devuan-keyring
Reading package lists... Done
Building dependency tree       
Reading state information... Done
devuan-keyring is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

is that a bug?? I can report it if you think it is.
I would have assumed a new server would need a new keyring??
'
Just trying to shed a little light - on my assumption

Last edited by garyz.dev1 (2017-10-21 14:45:33)

fungus · 2017-10-21 18:32:09

I was seeing some weird action a few days ago but thought I was doing something wrong, which I always do and forget to fix back what I broke. While on some recent minor upgrade I saw Debian's repository come up during update, and that was an instruction by devuan while using the onion addresses.
So, do the new reps have onion addresses as well and what are they?

Re: Fsmithred

No, no sydlexia here I am talking about pamac the equivalent of synaptic, not pacman the equivalent of apt/dpkg
It is pamac that has an app-tray-indicator for when an update to a package is available. It may have been originally a Manjaro invention that the AUR community passed to the Arch world, but don't take my word on it. It used to be simple and functional and they have made something that looks like an ubuntu gadget.

greenjeans · 2017-10-21 18:56:17

Great news, thanks fsmithred and all the other VUA's, we really appreciate all the hard work y'all put into Devuan!

fsmithred · 2017-10-21 21:39:12

Gary, it's not a bug. The key for the new repo was created Sep 4. I don't know what date it was added to the keyring, but I assume it was before your last upgrade. You already got it.

fungus, OK, pamac. Got it. Thanks. I'll bet they did that on purpose.
I don't know an onion address, but it might be in the works or already exist. Stay tuned.

UPDATE: This just in via irc:
"the onion link is here: https://devuan.org/
under "Packages""

and it goes to pkgmaster.devuan.org

fungus · 2017-10-21 22:49:33

Well that explains why I was having repository mix ups earlier this week, I was on this thing before it even got announced.

By the way, socks5 is one heck of a good way to make sure nobody messes with your packages between mirror and your disk.

I think this is really good work, it is appreciated. I hope most people will appreciate it too.

Last edited by fungus (2017-10-21 22:58:24)

Doge · 2017-10-22 11:57:33

Gratitude & appreciation for you and all the Dev1Devs.

fungus · 2017-10-24 13:44:50

While some of you are consumed in cock-fights off-topic there still is some ambiguity in what onion repositories should be.

I got a whole bunch of errors today from missing keys of repositories:
I switched all /merged/ to ../devuan/
Is this correct for all ascii, ceres, experimental? It was the only way I could get updated releases

All of the old tor://devuanfwojg73k6r.onion/merged/ are dead?

Then how come onion addresses have all shifted automatically to http://pkgmaster.devuan.org/merged/ when they are using merged instead of devuan?

Or was this some temporary outage?

Last edited by fungus (2017-10-24 13:50:23)

fungus · 2017-10-24 20:06:17

Katolaz from the DNG-list is trying to clarify

> > The repository is not updated and the previous index files will be used. GPG error: tor://devuanfwojg73k6r.onion/merged ascii InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BB23C00C61FC752C apt is telling you that you don'e have the key for that repo.
You must: # apt-get update # apt-get install devuan-keyring because amprolla3 is using a new signing key, which has been included in the latest devuan-keyring.
This was actually explained in the announcement to this list. I admit that we didn't announce the transition to amprolla3 for the onion address. Sorry for that.
> > I think I'm getting somewhere.
> > The merged repositories will not update because the key is expired. One would have to revert to the /devuan/ update the keyring and re-edit the repositories with the new key to be able to upgrade.
> > But what about proposed-updates, is this devuan or merged? jessie-proposed is under /devuan jessie-proposed-updates is under /devuan experimental is under /devuan The rest is under /merges, if I have not missed something.
> > I think there is proposed-security as well.
> > The installation I normally use and was checked frequently didn't have the same problem as the ones that have been unattended for a month or two. Somehow it seems as the keyring was updated before the pkgmaster deal and that makes the difference.
> That's because you need to install the latest devuan-keyring, as explained above. HTH KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ]

What he seems to not understand is that the repositories as they were could not be updated with the old key and the new key couldn't be updated with /merged
Only when the repositories were switched to /devuan was I able to update the key. Switching then back to /merged solved the issue but it would have been nice if there were more clarified instructions before some of us were "automatically" shifted to the new system.

AGAIN, the installation that was kept up to date frequently didn't have such a problem, while the ones who hadn't been updated since before the last keyring was issued were impossible to update as they were.

SO, if you, the forum member or outsider, have not updated your installation for a while and are on onion repositories chances are you may experience the same mess.

The underline of this is that "people" tend to respond a bit nasty here (Devuan) if they thing your question is putting blame on them, especially on that DNG list, when all you ask is for clarification to the lack of detailed instruction.

Amprolla3 was announced as a testing option for people to choose. Those utilizing onion repositories were automatically and after the fact shoved to be testing something new. And this made those with un-updated keyrings unable to update or upgrade anything. That is the bottom line!

golinux · 2017-10-24 20:16:20

Note there is no DNZ list. Corrected to DNG above. And here is the reference.

fungus · 2017-10-26 21:35:51

Deja-lost his-view .... I am imagining seeing things on forum that were on the list and list things that are on the forum.

Anyway, as there seems to be some confusion of the actual spelling of the entries in /etc/apt/sources.list, and after some clarification by fsmithred I gathered a huge list of repositories to choose from and what I believe is the correct entry.

From: fsmithred@****
To: dng@lists.dyne.org
My understanding is that for anything found under /merged on the server,
you should use /merged in your sources, and anything found ONLY under
/devuan needs to have /devuan in the sources.

deb https://pkgmaster.devuan.org/merged/ ascii main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-backports main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-proposed-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ascii-updates main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ ascii-proposed main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ ascii-proposed-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ ceres main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ experimental main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie-backports main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ jessie-proposed main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ jessie-proposed-backports main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ jessie-proposed-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie-proposed-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ jessie-updates main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ sid main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable-backports main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ stable-proposed main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable-proposed-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ stable-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing-backports main contrib non-free
deb https://pkgmaster.devuan.org/devuan/ testing-proposed main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing-proposed-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing-security main contrib non-free
deb https://pkgmaster.devuan.org/merged/ testing-updates main contrib non-free
deb https://pkgmaster.devuan.org/merged/ unstable main contrib non-free

deb tor://devuanfwojg73k6r.onion/ should be replaced to use the onion address or you could add tor+https://pkg.... to use tor without onion addresses.

I hope this helps to end the confusion. I think some of those repositories, like sid, may be empty but that is not a 404 error, or the side that has non-free may be empty. I hope that someone will verify this list is correct before my mistake or misperception spills more panic.

PS For https and tor you need apt-transport-https & apt-transport-tor otherwise substitute http from the list, right?

PS2 The tor-project repositories are:

deb tor://sdscoq7snqtznauu.onion/torproject.org/ jessie/stretch/buster/sid main  (choose a distribution to match)
deb tor://sdscoq7snqtznauu.onion/torproject.org/ tor-experimental-0.3.2.x-stretch main (switch stretch to one you want)
or https://deb.torproject.org/torproject.org

but you must first import the gpg key (look it up at their web page in the linux/debian/ubuntu instructions for tor)

fungus · 2017-12-08 04:52:46

There is one thing that I have yet to understand out of all this mystic repository structure.

merged

What exactly is merged? A selective Debian repository mirror with a Devuan repository?
If so, what edition of a Debian repository is used? Is it a frozen mirror copy of what was Debian back in July?
If not, how does Debian roll on a daily basis and how would Devuan ever be able to catch up?

Is Devuan really a rolling distribution?

After all this time I am clueless in answering these questions.

golinux · 2017-12-08 06:45:39

fungus wrote:

There is one thing that I have yet to understand out of all this mystic repository structure.
merged

The merged repo pulls in the filtered, unaltered pkgs from Debian that are allowed into Devuan.

What exactly is merged? A selective Debian repository mirror with a Devuan repository?
If so, what edition of a Debian repository is used?

Devuan jessie pulls from Debian jessie (oldstable)

Devuan ascii pulls from Debian stretch (current stable)

Devuan ceres is Debian sid (unstable)

Is Devuan really a rolling distribution?

I suppose that ceres could be considered a rolling distro.

After all this time I am clueless in answering these questions.

No kidding!

fungus · 2017-12-08 13:32:06

Like!

The officially official Devuan Forum!

#1 2017-10-20 21:57:56

Amprolla3 is out for testing

#2 2017-10-21 02:16:32

Re: Amprolla3 is out for testing

#3 2017-10-21 06:39:25

Re: Amprolla3 is out for testing

#4 2017-10-21 10:07:40

Re: Amprolla3 is out for testing

#5 2017-10-21 14:44:26

Re: Amprolla3 is out for testing

#6 2017-10-21 18:32:09

Re: Amprolla3 is out for testing

#7 2017-10-21 18:56:17

Re: Amprolla3 is out for testing

#8 2017-10-21 21:39:12

Re: Amprolla3 is out for testing

#9 2017-10-21 22:49:33

Re: Amprolla3 is out for testing

#10 2017-10-22 11:57:33

Re: Amprolla3 is out for testing

#11 2017-10-24 13:44:50

Re: Amprolla3 is out for testing

#12 2017-10-24 20:06:17

Re: Amprolla3 is out for testing

#13 2017-10-24 20:16:20

Re: Amprolla3 is out for testing

#14 2017-10-26 21:35:51

Re: Amprolla3 is out for testing

#15 2017-12-08 04:52:46

Re: Amprolla3 is out for testing

#16 2017-12-08 06:45:39

Re: Amprolla3 is out for testing

#17 2017-12-08 13:32:06

Re: Amprolla3 is out for testing

Board footer