Is the debian/devuan merge working right?

mknoop · 2019-04-20 17:26:59

For several days now, when I run apt-get update on beowulf, or ceres, it comes back with just Hits, and no Gets. The corresponding debian versions of buster and sid have been getting package upgrades, but these are not appearing in the devuan lists. The same thing is happening with ascii, but I do not have a corresponding debian system to compare it to.

I have trouble believing that all these debian upgraded packages require devuan modifications.

I am using the resource of http://deb.devuan.org/merged.

Was there something about the resource that I was supposed to modify?

Otherwise, it seems like the merge is not working.

Head_on_a_Stick · 2019-04-20 18:30:39

The repositories are updating for me:

23 packages can be upgraded. Run 'apt list --upgradable' to see them.

You should probably post all of your sources:

grep -v '^#\|^$' /etc/apt/sources.list{,.d/*}

rolfie · 2019-04-20 18:33:53

Got 3 updates on ASCII and 48 on Beowulf on the same resource using main contrib non-free and backports.

golinux · 2019-04-20 18:52:42

grep -v '^#\|^$' /etc/apt/sources.list{,.d/*}

That line is chicken scratches to me but that comma in {,.d/*} looks out of place so wondering if it is a typo.

Head_on_a_Stick · 2019-04-20 19:00:13

golinux wrote:

wondering if it is a typo.

No, it's brace expansion

Try the command yourself, I did check before posting it.

mknoop · 2019-04-20 21:49:10

on ceres I get :

/etc/apt/sources.list:deb http://deb.devuan.org/merged ceres main contrib non-free
/etc/apt/sources.list:deb http://deb.devuan.org/merged ascii main

on beowulf I get:

/etc/apt/sources.list:deb [ allow-insecure=yes ] http://deb.devuan.org/merged beowulf main contrib non-free
/etc/apt/sources.list:deb [ allow-insecure=yes ] http://deb.devuan.org/merged beowulf-updates main contrib non-free
/etc/apt/sources.list:deb [ allow-insecure=yes ] http://deb.devuan.org/merged beowulf-security main contrib non-free
/etc/apt/sources.list:deb http://deb.devuan.org/merged ascii main
/etc/apt/sources.list:deb http://deb.devuan.org/merged ascii-security main
grep: /etc/apt/sources.list.d/*: No such file or directory

and on ascii I get:

/etc/apt/sources.list:deb http://deb.devuan.org/merged ascii main contrib non-free
/etc/apt/sources.list:deb-src http://deb.devuan.org/merged ascii main contrib non-free
/etc/apt/sources.list:deb http://deb.devuan.org/merged ascii-security main contrib non-free
/etc/apt/sources.list:deb-src http://deb.devuan.org/merged ascii-security main contrib non-free
/etc/apt/sources.list:deb http://deb.devuan.org/merged ascii-updates main contrib non-free
/etc/apt/sources.list:deb-src http://deb.devuan.org/merged ascii-updates main contrib non-free
/etc/apt/sources.list:deb http://deb.devuan.org/merged ascii-backports main contrib non-free
/etc/apt/sources.list:deb http://deb.devuan.org/merged jessie main

I am still only getting Hits and no Gets on apt-get update.

Should I change the http to https everywhere?

Last edited by mknoop (2019-04-20 21:50:24)

rolfie · 2019-04-21 06:37:24

mknoop wrote:

/etc/apt/sources.list:deb http://deb.devuan.org/merged ceres main contrib non-free
/etc/apt/sources.list:deb http://deb.devuan.org/merged ascii main

You are mixing repositories. In this example remove ascii. Then it will work nicely.

Rolf

mknoop · 2019-04-21 07:00:37

Thanks for the try Rolf, but I commented out the ascii line and reran apt-get update. Nothing changed. That's not it.

sgage · 2019-04-21 13:07:13

I'm having trouble as well. I installed a fresh ascii, changed sources to beowulf. Apt update found 1363 packages to be updated. Apt dist-upgrade showed all the packages, asked Y/n, and when I proceeded:

Do you want to continue? [Y/n] 
Err:1 http://deb.devuan.org/merged beowulf/main amd64 wpasupplicant amd64 2:2.7+git20190128+0c1e29f-3
  404  Not Found [IP: 151.101.20.204 80]
Err:2 http://deb.devuan.org/merged beowulf/main amd64 libwebkit2gtk-4.0-37 amd64 2.22.7-1
  404  Not Found [IP: 151.101.20.204 80]
Err:3 http://deb.devuan.org/merged beowulf/main amd64 libjavascriptcoregtk-4.0-18 amd64 2.22.7-1
  404  Not Found [IP: 151.101.20.204 80]
Get:4 http://deb.devuan.org/merged beowulf/main amd64 gir1.2-webkit2-4.0 amd64 2.22.7-1 [126 kB]
Get:5 http://deb.devuan.org/merged beowulf/main amd64 gir1.2-javascriptcoregtk-4.0 amd64 2.22.7-1 [79.1 kB]
Fetched 205 kB in 0s (245 kB/s)                    
E: Failed to fetch http://deb.debian.org/debian/pool/main/w/wpa/wpasupplicant_2.7+git20190128+0c1e29f-3_amd64.deb  404  Not Found [IP: 151.101.20.204 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/w/webkit2gtk/libwebkit2gtk-4.0-37_2.22.7-1_amd64.deb  404  Not Found [IP: 151.101.20.204 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/w/webkit2gtk/libjavascriptcoregtk-4.0-18_2.22.7-1_amd64.deb  404  Not Found [IP: 151.101.20.204 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Any ideas?

fsmithred · 2019-04-21 15:04:40

I did an upgrade a few days ago, so there's nothing for me. I am able to install stuff from deb.devuan.org in beowulf. In another thread, we're still waiting for synaptic to enter beowulf. It went into buster a couple days ago.

Anyway, I have alerted the appropriate authorities. Today is a holiday, so responses might be slow.

nixer · 2019-04-21 15:34:00

I do not know, but I am wondering if this is a related issue?

This link to the main amprolla file shows this at the bottom:

2019/04/21 14:45:47 [WARN] http://deb.debian.org/debian/dists/bust … ents-arm64 failed: 404
2019/04/21 14:45:47 [WARN] http://deb.debian.org/debian/dists/bust … 28x128.tar failed: 404
2019/04/21 14:45:49 [WARN] http://deb.debian.org/debian/dists/bust … -amd64.yml failed: 404
2019/04/21 14:45:54 [WARN] http://deb.debian.org/debian/dists/bust … ps64el.yml failed: 404
2019/04/21 14:49:40 [WARN] http://deb.debian.org/debian/dists/stre … ce/Sources failed: 404
2019/04/21 14:49:40 [WARN] http://deb.debian.org/debian/dists/stre … nts-source failed: 404
2019/04/21 14:49:43 [INFO] Total incremental update time: 582.1237125396729
2019/04/21 14:50:08 [INFO] Total incremental update time: 7.0341596603393555
2019/04/21 14:55:04 [INFO] Total incremental update time: 2.9968421459198
2019/04/21 15:00:14 [INFO] Total incremental update time: 12.597147226333618
2019/04/21 15:05:04 [INFO] Total incremental update time: 3.4688239097595215
2019/04/21 15:10:04 [INFO] Total incremental update time: 2.7986111640930176
2019/04/21 15:15:05 [INFO] Total incremental update time: 4.079205751419067

Many, if not all packages currently show a "failed: 404", meaning, file is not found.

On my systems it shows no updates available so it does not try to download anything. However, I have also tried to update a beowulf and ceres install with no updates showing as available. Having no updates available for ceres (or beowulf) over a three day period is highly unusual. This could be that my systems were up to date when things went away. With the absence of no official word, I am merely offering one possible explanation.

Last edited by nixer (2019-04-21 15:36:08)

sgage · 2019-04-21 20:48:36

I'm trying to bring up a beowulf system by upgrading a fresh ascii installation. After changing the sources, apt update DOES find packages to update - some 1200+ at this point. apt dist-upgrade errors out as I indicated above. So the sources would seem to be correct, apt update parses everything properly, but apt upgrade can't actually get 'em, failing with

404  Not Found [IP: 200.236.31.3 80]

which seems to me to indicate some server 'plumbing' problem.

mknoop · 2019-04-22 17:25:02

I used my browser to search http://deb.devuan.org/merged/dists/ then I checked the directories ceres, beowulf, and ascii.

They all showed that the files InRelease, Release, and Release.gpg had last modified dates of 2019-04-17, so they have not been updated for 5 days so far.

guioQ · 2019-04-22 19:11:51

I'm having the same issue. The install (and then the upgrade to beowulf) went smooth, no errors whatsoever. The first error came up when I tried to install task-xfce-desktop
https://dev1galaxy.org/viewtopic.php?id=2803

yeti · 2019-04-23 07:07:40

guioQ wrote:

I'm having the same issue.

#heretoo
I just upgraded an ASCII install with XFCE to Beowulf and that was not really funny due to this hiccup... :-/
At lest reading that it is not PEBCAK is a bit of a relief.

mknoop · 2019-04-24 18:08:41

The original issue I posted in the first message has been resolved. Ceres, Beowulf, and Ascii are now all updating and upgrading packages correctly.

I cannot speak for the installation issues others have mentioned here.

Thank you.

sgage · 2019-04-24 19:19:01

mknoop wrote:

The original issue I posted in the first message has been resolved. Ceres, Beowulf, and Ascii are now all updating and upgrading packages correctly.
I cannot speak for the installation issues others have mentioned here.
Thank you.

Whatever resolved your issue also resolved my issue (as described in #9 and #12 in this thread).

Thanks for the heads-up!

abruening-iwt · 2019-07-12 10:50:45

Is this happening again? Time stamps are 07-07-2019 and I haven't gotten any updates for a while.

fsmithred · 2019-07-12 12:21:43

abruening-iwt wrote:

Is this happening again? Time stamps are 07-07-2019 and I haven't gotten any updates for a while.

Yes.

$ apt-cache policy firefox-esr
firefox-esr:
  Installed: 60.7.2esr-1~deb9u1
  Candidate: 60.8.0esr-1~deb9u1
  Version table:
     60.8.0esr-1~deb9u1 500
        500 http://auto.mirror.devuan.org/merged ascii-security/main amd64 Packages
         10 http://security.debian.org stretch/updates/main amd64 Packages
 *** 60.7.2esr-1~deb9u1 500
        500 http://pkgmaster.devuan.org/merged ascii-security/main amd64 Packages
        100 /var/lib/dpkg/status

The officially official Devuan Forum!

#1 2019-04-20 17:26:59

Is the debian/devuan merge working right?

#2 2019-04-20 18:30:39

Re: Is the debian/devuan merge working right?

#3 2019-04-20 18:33:53

Re: Is the debian/devuan merge working right?

#4 2019-04-20 18:52:42

Re: Is the debian/devuan merge working right?

#5 2019-04-20 19:00:13

Re: Is the debian/devuan merge working right?

#6 2019-04-20 21:49:10

Re: Is the debian/devuan merge working right?

#7 2019-04-21 06:37:24

Re: Is the debian/devuan merge working right?

#8 2019-04-21 07:00:37

Re: Is the debian/devuan merge working right?

#9 2019-04-21 13:07:13

Re: Is the debian/devuan merge working right?

#10 2019-04-21 15:04:40

Re: Is the debian/devuan merge working right?

#11 2019-04-21 15:34:00

Re: Is the debian/devuan merge working right?

#12 2019-04-21 20:48:36

Re: Is the debian/devuan merge working right?

#13 2019-04-22 17:25:02

Re: Is the debian/devuan merge working right?

#14 2019-04-22 19:11:51

Re: Is the debian/devuan merge working right?

#15 2019-04-23 07:07:40

Re: Is the debian/devuan merge working right?

#16 2019-04-24 18:08:41

Re: Is the debian/devuan merge working right?

#17 2019-04-24 19:19:01

Re: Is the debian/devuan merge working right?

#18 2019-07-12 10:50:45

Re: Is the debian/devuan merge working right?

#19 2019-07-12 12:21:43

Re: Is the debian/devuan merge working right?

Board footer