Re: [DNG] daedalus with chromiium
On Tue, 19 Apr 2022 00:41:53 +0200 Florian Zieboll via Dng wrote: > Dementia Sorry, I mean: just don't feed it! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] daedalus with chromiium
On Tue, 19 Apr 2022 07:48:59 +1000 Ralph Ronnquist wrote: > presuamably it now says daedalus with u rather than daedalas ? Dementia is a b1tch, as tr0lls are... onezero, f. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] daedalus with chromiium
presuamably it now says daedalus with u rather than daedalas ? Ralph. On Mon, Apr 18, 2022 at 04:22:54PM -0400, Haines Brown wrote: > I apologize for allowing Bob's message to get burried. > > On Sat, Apr 16, 2022 at 09:02:08PM -0600, Bob Proulx via Dng wrote: > > Haines Brown wrote: > > > I still get "Unable to locate package chromium". It seems that when I > > > did update/dist-upgrade after modifying sources.list to accommodate > > > daedulus I did not get the no InRelease file error. The chimaera > > > previously installed on this disk did not have chromium installed. > > > > What does this say for you? > > > > apt-cache policy chromium > > > > It should say something similar to this. > > > > root@clash:~# apt-cache policy chromium > > chromium: > > Installed: (none) > > Candidate: 100.0.4896.127-1 > > Version table: > > 100.0.4896.88-1 500 > > 500 http://deb.debian.org/debian daedalus/main amd64 Packages > > Yes it did > > I stumbled on the reason for my not getting a release file. The > line in my sources.list was > > deb http://deb.devuan.org/merged daedalas main non-free contrib > > I changed it to > > deb http://deb.devuan.org/merged daedalas main > > and the update/upgrade worked. I was then able restore the non-free > and contrib and install chromium. > > > > ___ > 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] daedalus with chromiium
I apologize for allowing Bob's message to get burried. On Sat, Apr 16, 2022 at 09:02:08PM -0600, Bob Proulx via Dng wrote: > Haines Brown wrote: > > I still get "Unable to locate package chromium". It seems that when I > > did update/dist-upgrade after modifying sources.list to accommodate > > daedulus I did not get the no InRelease file error. The chimaera > > previously installed on this disk did not have chromium installed. > > What does this say for you? > > apt-cache policy chromium > > It should say something similar to this. > > root@clash:~# apt-cache policy chromium > chromium: > Installed: (none) > Candidate: 100.0.4896.127-1 > Version table: > 100.0.4896.88-1 500 > 500 http://deb.debian.org/debian daedalus/main amd64 Packages Yes it did I stumbled on the reason for my not getting a release file. The line in my sources.list was deb http://deb.devuan.org/merged daedalas main non-free contrib I changed it to deb http://deb.devuan.org/merged daedalas main and the update/upgrade worked. I was then able restore the non-free and contrib and install chromium. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] daedalus with chromiium
Haines Brown wrote: > My message to the list seems to have gone amiss. This was it: Your message did not go amiss. The mailing list saw it. I replied to it. You have replied to my message therefore I know you saw my message too. Unfortunately it seems that though we are seeing each other's messages that we are definitely not communicating. I am sorry that we are "talking past each other". I tried to help. Sorry it did not work out. Bob signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] daedalus with chromiium
My message to the list seems to have gone amiss. This was it: On Sat, Apr 16, 2022 at 03:10:24PM +0900, Olaf Meeuwissen via Dng wrote: > Hi, > > Haines Brown writes: > > > A simple little question. I installed daedulus on a spare machine (no > > problems), but was dissapointed to find that chromium is not in the > > daedulus repository. What is that? > > I see > > $ apt-cache madison chromium > chromium | 100.0.4896.88-1 | http://deb.devuan.org/merged daedalus/main > amd64 Packages > chromium | 100.0.4896.88-1~deb11u1 | http://deb.devuan.org/merged > chimaera-security/main amd64 Packages > > Seems to be there alright. Thanks, Olaf. I still get "Unable to locate package chromium". It seems that when I did update/dist-upgrade after modifying sources.list to accommodate daedulus I did not get the no InRelease file error. The chimaera previously installed on this disk did not have chromium installed. I tried $ sudo apt-get --allowUnauthenticated install chromium, but this command was unable to locate chromium. I did not create a file /etc/apt/apt.conf/d/99myown with line APT::Get::AllowUnauthenticated "true"; because very insecure. In any case I'm not sure it would work ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] daedalus with chromiium
Haines Brown wrote: > I still get "Unable to locate package chromium". It seems that when I > did update/dist-upgrade after modifying sources.list to accommodate > daedulus I did not get the no InRelease file error. The chimaera > previously installed on this disk did not have chromium installed. What does this say for you? apt-cache policy chromium It should say something similar to this. root@clash:~# apt-cache policy chromium chromium: Installed: (none) Candidate: 100.0.4896.127-1 Version table: 100.0.4896.88-1 500 500 http://deb.debian.org/debian daedalus/main amd64 Packages If it does not then investigate why not. It's just possible that having changed suites that apt is waiting for an acknowledgment. This was added in some recent year. --allow-releaseinfo-change Allow the update command to continue downloading data from a repository which changed its information of the release contained in the repository indicating e.g a new major release. APT will fail at the update command for such repositories until the change is confirmed to ensure the user is prepared for the change. See also apt-secure(8) for details on the concept and configuration. Specialist options (--allow-releaseinfo-change-field) exist to allow changes only for certain fields like origin, label, codename, suite, version and defaultpin. See also apt_preferences(5). Configuration Item: Acquire::AllowReleaseInfoChange. To acknowledge the change do this as root. apt-get update --allow-releaseinfo-change apt-get update Then follow the acknowledgment by another update. It's confusing but as far as I can see from documentation and experimentation it needs both of those. The first to acknowledge and the second to actually do the update of the new Packages indexes. After that everything should be available. > I tried $ sudo apt-get --allowUnauthenticated install chromium, but > this command was unable to locate chromium. > > I did not create a file /etc/apt/apt.conf/d/99myown with line > > APT::Get::AllowUnauthenticated "true"; > > because very insecure. In any case I'm not sure it would work The main useful purpose of --allow-unauthenticated is for *older* releases in the archive that have expired keys. Because those are archived they are not getting signed with updated keys. The original signatures are still as indicative as before but now they have expired. --allow-unauthenticated Ignore if packages can't be authenticated and don't prompt about it. This can be useful while working with local repositories, but is a huge security risk if data authenticity isn't ensured in another way by the user itself. The usage of the Trusted option for sources.list(5) entries should usually be preferred over this global override. Configuration Item: APT::Get::AllowUnauthenticated. Daedalus is currently active and there should be no need to use the --allow-unauthenticated option. It's also useful for unsigned local repositories and other uses too. Not to give the idea that it isn't ever useful. But it worries me to be used for Daedalus on the currently active reposities. Bob signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] daedalus with chromiium
On Sat, Apr 16, 2022 at 03:10:24PM +0900, Olaf Meeuwissen via Dng wrote: > Hi, > > Haines Brown writes: > > > A simple little question. I installed daedulus on a spare machine (no > > problems), but was dissapointed to find that chromium is not in the > > daedulus repository. What is that? > > I see > > $ apt-cache madison chromium > chromium | 100.0.4896.88-1 | http://deb.devuan.org/merged daedalus/main > amd64 Packages > chromium | 100.0.4896.88-1~deb11u1 | http://deb.devuan.org/merged > chimaera-security/main amd64 Packages > > Seems to be there alright. Thanks, Olaf. I still get "Unable to locate package chromium". It seems that when I did update/dist-upgrade after modifying sources.list to accommodate daedulus I did not get the no InRelease file error. The chimaera previously installed on this disk did not have chromium installed. I tried $ sudo apt-get --allowUnauthenticated install chromium, but this command was unable to locate chromium. I did not create a file /etc/apt/apt.conf/d/99myown with line APT::Get::AllowUnauthenticated "true"; because very insecure. In any case I'm not sure it would work ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] daedalus with chromiium
Hi, Haines Brown writes: > A simple little question. I installed daedulus on a spare machine (no > problems), but was dissapointed to find that chromium is not in the > daedulus repository. What is that? I see $ apt-cache madison chromium chromium | 100.0.4896.88-1 | http://deb.devuan.org/merged daedalus/main amd64 Packages chromium | 100.0.4896.88-1~deb11u1 | http://deb.devuan.org/merged chimaera-security/main amd64 Packages Seems to be there alright. Hope this helps, -- Olaf MeeuwissenFSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] daedalus with chromiium
A simple little question. I installed daedulus on a spare machine (no problems), but was dissapointed to find that chromium is not in the daedulus repository. What is that? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
