Re: [DNG] reportbug is the stable repository
On Sun, Jul 23, 2017 at 05:44:14PM -0400, Boruch Baum wrote: > > Funny, Why is it that I only get that kind of response from people who > only make useless unconstructive and unhelpful comments? It doesn't > sound that you have been following this thread too closely. The source > of the problem was a line of code pushed by devuan into my > /etc/apt/apt.conf file at some point. My guess, and its only a guess, is > that the issue hasn't been widespread because most user re-installed > from scratch in the transition from beta. Again just for clarity: there are hundreds of users in this list that have been using Devuan since Jessie Beta, without reinstalling from scratch, and none has ever seen your problems. So your guess does not seem to be correct. Devuan has not pushed anything to your apt.conf. You are in fact mixing repos from different distros and different releases, and, traditionally, if you do that in De??an you are on your own. HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On 2017-07-21 19:06, KatolaZ wrote: > On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote: > > On 2017-07-22 00:23, Ralph Ronnquist wrote: > > > Boruch Baum wrote on 21/07/17 23:50: > > > > Where else should I be looking? > > > > > > Perhaps you've set "APT::Default-Release "jessie";" ? > > > > > > Without that, you'll get the more balanced pinning of 500 and 100. > > > I think I saw some Debian bug report (on apt?) for this. > > > > Thanks, Ralph! > > > > That's good news and solved the immediate mystery, but isn't yet an > > entire solution. Ok, Ralph, your fix was key, but I had to follow it up with a few other steps. After some testing, here's some information for the benefit of the list and other devuan users, about what seems to be working for me. 1] First some background, The useful command for this scenario is 'apt-cache policy', which displays all the available versions of a package, each's pin value, which is installed, and which apt would currently want to install (labeled the "candidate"). 1.1] If you are pulling in the translation sections of debian repositories so that you can benefit from being able to locally read long package descriptions in 'apt-cache show', you'll find that the additional entries make it a bit more difficult to read the output of 'apt-cache policy'. For convenience, you can just temporarily comment out those lines in you /etc/apt/sources.list while evaluating 'apt-cache policy' output, and uncomment the lines afterwards. 2] The only entry in my /etc/apt/apt.conf file was the one Ralph pointed out was trouble. I eventually deleted the file. 3] Likewise, there were two files in /etc/apt/preferences.d, 'discourage-testing' and 'discourage-backports' that didn't suit my use case. After testing, I deleted them and incorporated my alternative into file '/etc/apt/preferences', below. 3.3] My use case is a Jessie install, with occasional needs or desires for more up-to-date packages, so I need to be able to sanely pull in and manage packages from backports and testing. I also want allowance to be able to pull in packages from unstable for when debian declares a package freeze, which can lock out packages from entering testing for months (usually there's just a ten day lag for packages to auto-migrate from unstable to testing). 4] My current file "/etc/apt/preferences" looks like this, and seems to do the trick. It meets the criteria of my use case, it makes no wild demands insisting that I do close to the equivalent of a dist-upgrade to ceres, and it seems to properly decide when to upgrade packages that had been previously installed with the default devuan pins of 990 and 500. 4.1] To give you a practical measure of the effect of this solution, without it 'apt-get upgrade' wanted to install 1,248 packages, and with this config, just three. #+BEGIN_SRC conf # Apt will also pull in pinning instructions from any readable file in # '/etc/apt/preferences.d', so check there when maintaining this # function. Package: * Pin: release o=Devuan,n=jessie Pin-Priority: 800 Package: * Pin: release o=Devuan,a=jessie-backports Pin-Priority: 750 Package: * Pin: release o=Devuan,a=ascii Pin-Priority: 400 Package: * Pin: release o=Devuan,a=ascii-backports Pin-Priority: 350 Package: * Pin: release o=Devuan,n=ceres Pin-Priority: 200 #+END_SRC 5] That's it! If anyone is tempted to duplicate this, I recommend waiting as long as you can bear and contacting me off-list for an update. > I am very glad you solved your problem, in the end. Thanks for the (pre-mature) verdict. I solved the problem this afternoon ago, and included a report above for the benefit of others. > For the future, please try to be more considerate before rushing to > report the "incompetent" behaviour of something of somebody else :) Funny, Why is it that I only get that kind of response from people who only make useless unconstructive and unhelpful comments? It doesn't sound that you have been following this thread too closely. The source of the problem was a line of code pushed by devuan into my /etc/apt/apt.conf file at some point. My guess, and its only a guess, is that the issue hasn't been widespread because most user re-installed from scratch in the transition from beta. > WithLove XOXO > P.S.: Concerning the one thousand-two hundred-and-counting packages to > upgrade, it looks like your system has remained stuck somewhere close > to late 2015 or early 2016, so it's normal to have that many packages > to be upgraded in 18 months, especially if you enable -backports, > -updates, and -security. No. Totally off-the-mark. See above. -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On Fri, 21 Jul 2017 22:21:53 -0400, Hendrik wrote in message <20170722022153.gb8...@topoi.pooq.com>: > On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote: > > > The bad news is that if this is the only step I take, "apt-get" will > > want to upgrade 1248 packages (it looks more impressive when I > > write it out . . One Thousand, Two Hundred and Forty Eight > > packages) with a download size of 608 Mb. > > There really needs to be a way of doing this in a staged manner, > i.e., not all at once, for those who don't have huge disk space > available. ..there is, use aptitude, "u" to update, "U" to upgrade, ":" to pick stuff to hold back until "next time." -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote: > The bad news is that if this is the only step I take, "apt-get" will > want to upgrade 1248 packages (it looks more impressive when I write it > out . . One Thousand, Two Hundred and Forty Eight packages) with a > download size of 608 Mb. There really needs to be a way of doing this in a staged manner, i.e., not all at once, for those who don't have huge disk space available. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
I wrote: > All the time, a lot of people we stood on the sidelines willing them to fail. Oops, s/we/were/ Personally I was watching and thinking "that's one hell of a task, I'm a bit sceptical* but I sure as heck hope they manage it". * Not knowing who these veterans were, and their level of skill and determination. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
Boruch Baum wrote: > The bad news is that if this is the only step I take, "apt-get" will > want to upgrade 1248 packages (it looks more impressive when I write it > out . . One Thousand, Two Hundred and Forty Eight packages) with a > download size of 608 Mb. What if, instead of doing "apt-get [dist-]upgrade" you do "apt-get install reportbug" ? That will upgrade reportbug and only other packages that need an upgrade to satisfy dependencies. Boruch Baum wrote: > 3] Isn't it doing something quite unacceptable that it should never have > been doing in the first place? In an ideal world, yes. But bear in mind that a small bunch of people decided to do something practical about the cancer of systemd and fork Debian. Debian has been going for a lng time, and has had a lng time to get all the infrastructure into place. Devuan had to start from scratch, work out a way to make a repository system work with split sources (most from Debian, some from Devuan), fix/replace those key packages that were "broken" by systemd but weren't really optional, organise hosting for everything, etc, etc. All the time, a lot of people we stood on the sidelines willing them to fail. Against all this, this small bunch of people who are clearly much cleverer than I in these matters, made it happen. There were a few rough edges, and probably will be for some time - lots of systemd to cure, too few volunteers to do it. Lets try and stay positive shall we ? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On Fri, Jul 21, 2017 at 11:45:23AM -0400, Boruch Baum wrote: > On 2017-07-22 00:23, Ralph Ronnquist wrote: > > Boruch Baum wrote on 21/07/17 23:50: > > > Where else should I be looking? > > > > Perhaps you've set "APT::Default-Release "jessie";" ? > > > > Without that, you'll get the more balanced pinning of 500 and 100. > > I think I saw some Debian bug report (on apt?) for this. > > Thanks, Ralph! > > That's good news and solved the immediate mystery, but isn't yet an > entire solution. > > The good news is that, indeed, that was the only line in my > /etc/apt/apt.conf file, and upon being commented out, running apt-cache > policy on a package such as reportbug did report all 990 pinnings gone. > -_- I am very glad you solved your problem, in the end. For the future, please try to be more considerate before rushing to report the "incompetent" behaviour of something of somebody else :) Here at Devuan we naturally tend to love unconditionally all those who are in good faith, irrespective or their own "moments" (and we all have ours). But you might get much nastier replies and worse reactions elsewhere ;) WithLove KatolaZ P.S.: Concerning the onethousand-twohundred-and-counting packages to upgrade, it looks like your system has remained stuck somewhere close to late 2015 or early 2016, so it's normal to have that many packages to be upgraded in 18 months, especially if you enable -backports, -updates, and -security. -- [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On 2017-07-22 00:23, Ralph Ronnquist wrote: > Boruch Baum wrote on 21/07/17 23:50: > > Where else should I be looking? > > Perhaps you've set "APT::Default-Release "jessie";" ? > > Without that, you'll get the more balanced pinning of 500 and 100. > I think I saw some Debian bug report (on apt?) for this. Thanks, Ralph! That's good news and solved the immediate mystery, but isn't yet an entire solution. The good news is that, indeed, that was the only line in my /etc/apt/apt.conf file, and upon being commented out, running apt-cache policy on a package such as reportbug did report all 990 pinnings gone. The bad news is that if this is the only step I take, "apt-get" will want to upgrade 1248 packages (it looks more impressive when I write it out . . One Thousand, Two Hundred and Forty Eight packages) with a download size of 608 Mb. The over-riding news is that it's getting too close to Shabbat to be starting to mess with this kind of thing, so continuing this will have to wait until Saturday night or Sunday. -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
Boruch Baum wrote on 21/07/17 23:50: On 2017-07-21 14:14, KatolaZ wrote: On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote: Just to clarify, and since you are talking about "default" pin levels: the default pin level of standard Devuan repositories is 500. The default for backports and experimental is 100. So I can't explain where does your "default" 990 come from, except for an obvious mangling with pins on your side. Devuan is far from being perfect, and has several glitches, but please let's try to be honest and do not attribute our own glitches to Devuan as well: it would just be totally unfair :) I've just now looked AGAIN manually and using grep, and haven't found anywhere in /etc/apt or its sub-directories any explicit pin for anything 990. Where else should I be looking? Perhaps you've set "APT::Default-Release "jessie";" ? Without that, you'll get the more balanced pinning of 500 and 100. I think I saw some Debian bug report (on apt?) for this. Ralph. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On Fri, Jul 21, 2017 at 09:40:27AM -0400, Boruch Baum wrote: [cut] > > 2] Isn't it a legitimate devuan package from a legitimate currently >supported devuan repository? if you are not using the 6.6.3+devuan1.3 version, then it's not a package in a legitimate currently supported devuna repository. > > 3] Isn't it doing something quite unacceptable that it should never have >been doing in the first place? > > 4] Sholdn't it be fixed, or removed, and / or have users pointed to an >upgrade path? > I have said alredy that you must use reportbug-6.6.3+devuan1.3 in jessie. The other version you are mentioning was removed from Devuan before RC1 came out. And I am convinced that you must still have a pin somewhere in /etc/apt/preferences.d, because 990 is not a default pin level anywhere in devuan. This is what I get on ascii: # apt-cache policy reportbug reportbug: Installed: 7.1.6+devuan2.1 Candidate: 7.1.6+devuan2.1 Version table: *** 7.1.6+devuan2.1 500 500 http://auto.mirror.devuan.org/merged ascii/main amd64 Packages 500 http://auto.mirror.devuan.org/merged ascii/main i386 Packages 500 http://packages.devuan.org/devuan ascii/main amd64 Packages 500 http://packages.devuan.org/devuan ascii/main i386 Packages 100 /var/lib/dpkg/status # ls /etc/apt/preferences.d/ avoid-systemd # cat /etc/apt/preferences.d/avoid-systemd Package: systemd-sysv Pin: release o=Debian Pin-Priority: -1 # and I keep avoid-systemd only for romatic reasons, since it is not needed any more since jessie beta (May 2016). My2Cents KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On 2017-07-21 14:14, KatolaZ wrote: > On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote: > > Just to clarify, and since you are talking about "default" pin levels: > the default pin level of standard Devuan repositories is 500. The > default for backports and experimental is 100. So I can't explain > where does your "default" 990 come from, except for an obvious > mangling with pins on your side. > > Devuan is far from being perfect, and has several glitches, but please > let's try to be honest and do not attribute our own glitches to Devuan > as well: it would just be totally unfair :) I've just now looked AGAIN manually and using grep, and haven't found anywhere in /etc/apt or its sub-directories any explicit pin for anything 990. Where else should I be looking? -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On 2017-07-21 14:01, KatolaZ wrote: > On Fri, Jul 21, 2017 at 08:46:27AM -0400, Boruch Baum wrote: > > On 2017-07-21 13:24, KatolaZ wrote: > > > Please check this first, since dozens of people are using reportbug > > > from jessie, and their bugs are correctly reported to bugs.devuan.org. > > > > Enzo, I should add that though I manually submitted THREE bug reports to > > devuan this morning, I have received neither confirmation nor email > > bounce from any, nor does a search at http://bugs.devuan.org/ show > > record of reciept of any of my emails. Attached is a copy of one of the > > three emailed bug reports. > > You should exercise some patience, please :) The bug reports are > processed in batches. Your emails arrived on the server aroun 11:40, > 11:50, 12:30 UTC time, and have been processed. You should have > received confirmation emails by now. Also, the pages on > bugs.devuan.org are not updated immediately, so your bugs will appear > there soon. Just got confirmation, now. My expectation was based upon the debian operational method, which is immediate. Since most of your target "audience" are debian "defectors" with that expectation, maybe add a comment message in reportbug and the website saying what you just wrote me. Thanks. -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On 2017-07-21 13:57, KatolaZ wrote: > On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote: > > Thanks for a quick response. > > > > > > On 2017-07-21 13:24, KatolaZ wrote: > > > Which version of reportbug are you using? > > > > The offending version was 6.6.6~bpo8+1, and the upgraded (current) > > version is 7.1.6+devuan2.1. > > So it was not Devuan's incompetence, for once :) Well, that's a bit premature. And possibly over-sensitive . . . > > > > > jessie has 6.6.3+devuan1.3, > > > > That version does show up on my apt-cache policy output, pinned to the > > default 990 from http://auto.mirrors.devuan.org/merged jessie/main. > > > > However, version 6.6.6~bpo8+1 was likewise pinned to the default 990 > > from http://auto.mirrors.devuan.org/merged jessie-backports/main > > So it's not installed because you have pinned a repo manually, which > again is not Devuan's fault 1] Not so, sherlock. Better to ask me: Did you Boruch pin that manually? No, Enzo, I did no such thing. 1.1] But Boruch, did you double-check? Yes, Enzo, I did, and there is something curious, in that I don't see anywhere in /etc/apt anything being pinned explicitly to value 990. Where else should I look? 2] Isn't it a legitimate devuan package from a legitimate currently supported devuan repository? 3] Isn't it doing something quite unacceptable that it should never have been doing in the first place? 4] Sholdn't it be fixed, or removed, and / or have users pointed to an upgrade path? -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On Fri, Jul 21, 2017 at 02:01:46PM +0100, KatolaZ wrote: [cut] > > Hi, > > You should exercise some patience, please :) The bug reports are > processed in batches. Your emails arrived on the server aroun 11:40, > 11:50, 12:30 UTC time, and have been processed. You should have > received confirmation emails by now. Also, the pages on > bugs.devuan.org are not updated immediately, so your bugs will appear > there soon. > ...and just to clarify, since we talk about glitches: there was indeed a small glitch with processing one of your three bug reports, due to a recent change we introduced to correctly handle certain kinds of follow-up messages. That glitch actually caused the slightly-larger-than-usual delay on delivering the remaining confirmation emails. Sorry for that. Thanks a lot for reporting it :) HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote: [cut] > > That version does show up on my apt-cache policy output, pinned to the > default 990 from http://auto.mirrors.devuan.org/merged jessie/main. > > However, version 6.6.6~bpo8+1 was likewise pinned to the default 990 > from http://auto.mirrors.devuan.org/merged jessie-backports/main > Just to clarify, and since you are talking about "default" pin levels: the default pin level of standard Devuan repositories is 500. The default for backports and experimental is 100. So I can't explain where does your "default" 990 come from, except for an obvious mangling with pins on your side. Devuan is far from being perfect, and has several glitches, but please let's try to be honest and do not attribute our own glitches to Devuan as well: it would just be totally unfair :) HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On Fri, Jul 21, 2017 at 08:46:27AM -0400, Boruch Baum wrote: > On 2017-07-21 13:24, KatolaZ wrote: > > Please check this first, since dozens of people are using reportbug > > from jessie, and their bugs are correctly reported to bugs.devuan.org. > > Enzo, I should add that though I manually submitted THREE bug reports to > devuan this morning, I have received neither confirmation nor email > bounce from any, nor does a search at http://bugs.devuan.org/ show > record of reciept of any of my emails. Attached is a copy of one of the > three emailed bug reports. > Hi, You should exercise some patience, please :) The bug reports are processed in batches. Your emails arrived on the server aroun 11:40, 11:50, 12:30 UTC time, and have been processed. You should have received confirmation emails by now. Also, the pages on bugs.devuan.org are not updated immediately, so your bugs will appear there soon. Best Regards KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On Fri, Jul 21, 2017 at 08:39:50AM -0400, Boruch Baum wrote: > Thanks for a quick response. > > > On 2017-07-21 13:24, KatolaZ wrote: > > Which version of reportbug are you using? > > The offending version was 6.6.6~bpo8+1, and the upgraded (current) > version is 7.1.6+devuan2.1. So it was not Devuan's incompetence, for once :) > > > jessie has 6.6.3+devuan1.3, > > That version does show up on my apt-cache policy output, pinned to the > default 990 from http://auto.mirrors.devuan.org/merged jessie/main. > > However, version 6.6.6~bpo8+1 was likewise pinned to the default 990 > from http://auto.mirrors.devuan.org/merged jessie-backports/main So it's not installed because you have pinned a repo manually, which again is not Devuan's fault > > > which knows about bugs.devuan.org and correctly uses it, unless you > > have any other reportbug custom configuration (which is honoured by > > reportbug and overrides the defaults). > > I just now double-checked both my ~/reportbugrc and the version at /etc. > No relevant customization. If you are on jessie, just please install the version of reportbug that comes with Jessie. If you are using ascii, please use the version in ascii. HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On 2017-07-21 13:24, KatolaZ wrote:
> Please check this first, since dozens of people are using reportbug
> from jessie, and their bugs are correctly reported to bugs.devuan.org.
Enzo, I should add that though I manually submitted THREE bug reports to
devuan this morning, I have received neither confirmation nor email
bounce from any, nor does a search at http://bugs.devuan.org/ show
record of reciept of any of my emails. Attached is a copy of one of the
three emailed bug reports.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
From: Boruch Baum
To: Devuan Bug Tracking System
Subject: mutt: Install missing required dependencies (libxapian30)
Message-ID: <20170721122023.udbzgvx3zvocf...@e15-2016.optimum.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: NeoMutt/20170113 (1.7.2)
Status: RO
Subject: mutt: Install missing required dependencies (libxapian30)
Package: mutt
Version: 1.7.2-1
Severity: serious
Dear Maintainer,
Upon upgrading `mutt' from the stable to testing repositories, mutt
ceased to function, offering the following error message:
#+BEGIN_SRC conf
mutt: symbol lookup error: /usr/lib/x86_64-linux-gnu/libnotmuch.so.4:
undefined symbol:
_ZN6Xapian9Compactor26resolve_duplicate_metadataERKNSt7__cxx1112basic_strin=
gIcSt11char_traitsIcESaIcEEEmPS7_
#+End_SRC
Performing the following fixed the problem for me:
#+BEGIN_SRC conf
apt-get install libxapian30
The following packages will be upgraded:
libxapian-dev libxapian30 xapian-tools
#+END_SRC
-- Package-specific info:
NeoMutt 20170113 (1.7.2)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.
System: Linux 4.9.0-2-grsec-amd64 (x86_64)
libidn: 1.29 (compiled with 1.33)
hcache backends: tokyocabinet
Compiler:
Using built-in specs.
COLLECT_GCC=3Dgcc
COLLECT_LTO_WRAPPER=3D/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion=3D'Debian 6.3.0-2' -=
-with-bugurl=3Dfile:///usr/share/doc/gcc-6/README.Bugs --enable-languages=
=3Dc,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=3D/usr --program-suffi=
x=3D-6 --program-prefix=3Dx86_64-linux-gnu- --enable-shared --enable-linker=
-build-id --libexecdir=3D/usr/lib --without-included-gettext --enable-threa=
ds=3Dposix --libdir=3D/usr/lib --enable-nls --with-sysroot=3D/ --enable-clo=
cale=3Dgnu --enable-libstdcxx-debug --enable-libstdcxx-time=3Dyes --with-de=
fault-libstdcxx-abi=3Dnew --enable-gnu-unique-object --disable-vtable-verif=
y --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib -=
-disable-browser-plugin --enable-java-awt=3Dgtk --enable-gtk-cairo --with-j=
ava-home=3D/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home --wit=
h-jvm-root-dir=3D/usr/lib/jvm/java-1.5.0-gcj-6-amd64 --with-jvm-jar-dir=3D/=
usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 --with-arch-directory=3Damd64 --=
with-ecj-jar=3D/usr/share/java/eclipse-ecj.jar --with-target-system-zlib --=
enable-objc-gc=3Dauto --enable-multiarch --with-arch-32=3Di686 --with-abi=
=3Dm64 --with-multilib-list=3Dm32,m64,mx32 --enable-multilib --with-tune=3D=
generic --enable-checking=3Drelease --build=3Dx86_64-linux-gnu --host=3Dx86=
_64-linux-gnu --target=3Dx86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20161229 (Debian 6.3.0-2)
Configure options: '--build=3Dx86_64-linux-gnu' '--prefix=3D/usr' '--includ=
edir=3D\${prefix}/include' '--mandir=3D\${prefix}/share/man' '--infodir=3D\=
${prefix}/share/info' '--sysconfdir=3D/etc' '--localstatedir=3D/var' '--dis=
able-silent-rules' '--libdir=3D\${prefix}/lib/x86_64-linux-gnu' '--libexecd=
ir=3D\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' '--disabl=
e-dependency-tracking' '--with-mailpath=3D/var/mail' '--enable-compressed' =
'--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--ena=
ble-imap' '--enable-smtp' '--enable-pop' '--enable-sidebar' '--enable-nntp'=
'--enable-notmuch' '--disable-fmemopen' '--with-curses' '--with-gnutls' '-=
-with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' '--without-gdbm' '=
--without-bdb' '--without-qdbm' '--with-tokyocabinet' 'build_alias=3Dx86_64=
-linux-gnu' 'CFLAGS=3D-g -O2 -fdebug-prefix-map=3D/build/mutt-K2ak0h/mutt-1=
=2E7.2=3D. -fstack-protector-strong -Wformat -Werror=3Dformat-security' 'LD=
FLAGS=3D-Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=3D-Wdate-time -D_FORTIFY_SOURCE=
=3D2'
Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 -fdebug-prefix-ma=
p=3D/build/mutt-K2ak0h/mutt-1.7.2=3D. -fstack-protector-strong -Wformat -We=
rror=3Dformat-security -fno-delete-null-pointer-checks
Compile options:
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME
+DEBUG +DL_STANDAL
Re: [DNG] reportbug is the stable repository
Thanks for a quick response. On 2017-07-21 13:24, KatolaZ wrote: > Which version of reportbug are you using? The offending version was 6.6.6~bpo8+1, and the upgraded (current) version is 7.1.6+devuan2.1. > jessie has 6.6.3+devuan1.3, That version does show up on my apt-cache policy output, pinned to the default 990 from http://auto.mirrors.devuan.org/merged jessie/main. However, version 6.6.6~bpo8+1 was likewise pinned to the default 990 from http://auto.mirrors.devuan.org/merged jessie-backports/main > which knows about bugs.devuan.org and correctly uses it, unless you > have any other reportbug custom configuration (which is honoured by > reportbug and overrides the defaults). I just now double-checked both my ~/reportbugrc and the version at /etc. No relevant customization. -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] reportbug is the stable repository
On Fri, Jul 21, 2017 at 08:15:59AM -0400, Boruch Baum wrote: > > Earlier today, I filed a bug report against the devuan testing version > of 'mutt', but because I was using the stable version of devuan, and the > stable version of reportbug, the report went to debian. > > Now, that was incompetent. Was it incompetent of me or of devuan or > both? Which version of reportbug are you using? jessie has 6.6.3+devuan1.3, which knows about bugs.devuan.org and correctly uses it, unless you have any other reportbug custom configuration (which is honoured by reportbug and overrides the defaults). Please check this first, since dozens of people are using reportbug from jessie, and their bugs are correctly reported to bugs.devuan.org. Thanks KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] reportbug is the stable repository
Earlier today, I filed a bug report against the devuan testing version of 'mutt', but because I was using the stable version of devuan, and the stable version of reportbug, the report went to debian. Now, that was incompetent. Was it incompetent of me or of devuan or both? Updating a recipient email address in a package isn't some major effort that requires new testing repository dependencies - it's probably just a debian quilt patch, and a trivial one at that. The results are: 1] wasteful and unnecessary period of confusion and correspondence to clear up the situation; 2] increased negative reputation for the project in that it's not playing nicely with its parent project; 3] increased wariness of reporting bugs; 4] increased wariness of depending on the distribution for anything critical. 4.1] What an observer to the project can expect to see is a community expending much time and effort engaging in all kinds of very lengthy off-topic discussions, with an *extremely* low signal-noise-ratio, while certificates are left to expire multiple times, where scheduled outages are only announced to the "campfire" list, not the "announce" or "developer" list, and where bugs for the stable release are sent (only) to another distribution. Was this constructive? -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
