Re: [DNG] trash
Hi, Florian Zieboll writes: > On Sun, 28 May 2017 09:17:05 -0400 > Hendrik Boom wrote: > >> The only one I have an idea what it's for is sane-utils. Presumably >> access to scanners. > > As mentioned on this list some days ago, sane-utils is not necessary to > run a local scanner. It provides saned to remotely access a local > scanner. I just had a look: it also includes the commands scanimage and > sane-find-scanner (which probably would work perfectly fine with a > broken libsystemd0 dependency). So the vast majority of users won't > need it. IIRC, a sane developer had replied to that thread and said > that also saned just checks for the existence of libsystemd0 but does > not need it at all. So the "dependency" is null and could be removed. You remember correctly ;-) It's not a "dependency", it's a compile-time option. To get rid of the Depends:, you will need to drop libsystemd-dev (and maybe dh-systemd) from the debian/control file and rebuild the package. That's all. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF 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
Re: [DNG] trash
On Mon, May 29, 2017 at 08:16:28PM +0900, Olaf Meeuwissen wrote: > Florian Zieboll writes: > > IIRC, a sane developer had replied to that thread and said > > that also saned just checks for the existence of libsystemd0 but does > > not need it at all. So the "dependency" is null and could be removed. > > You remember correctly ;-) > > It's not a "dependency", it's a compile-time option. To get rid of the > Depends:, you will need to drop libsystemd-dev (and maybe dh-systemd) > from the debian/control file and rebuild the package. That's all. Which actually are (Build-)Dependencies, that turn into actual Dependencies once built. But indeed, like for the vast majority of infested packages, it's all it takes -- most upstream developers are not evil, and DTRT when systemd headers are not available. Even if they're systemd apologists themselves, many projects want to work on BSD and so on. A debdiff attached, compile-tested only (I have no scanner hardware). Meow! -- Don't be racist. White, amber or black, all beers should be judged based solely on their merits. Heck, even if occasionally a cider applies for a beer's job, why not? On the other hand, corpo lager is not a race. diff -Nru sane-backends-1.0.25/debian/changelog sane-backends-1.0.25/debian/changelog --- sane-backends-1.0.25/debian/changelog 2017-05-21 10:04:48.0 +0200 +++ sane-backends-1.0.25/debian/changelog 2017-05-29 13:24:39.0 +0200 @@ -1,3 +1,10 @@ +sane-backends (1.0.25-4.1.0nosystemd1) unstable; urgency=medium + + * Non-maintainer upload. + * Cure systemd infestation. + + -- Adam Borowski Mon, 29 May 2017 13:24:39 +0200 + sane-backends (1.0.25-4.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru sane-backends-1.0.25/debian/control sane-backends-1.0.25/debian/control --- sane-backends-1.0.25/debian/control 2017-05-21 10:04:48.0 +0200 +++ sane-backends-1.0.25/debian/control 2017-05-29 13:23:16.0 +0200 @@ -8,7 +8,6 @@ autoconf, chrpath, debhelper (>= 10), - dh-systemd, gettext, libavahi-client-dev, libcam-dev [kfreebsd-any], @@ -17,7 +16,6 @@ libieee1284-3-dev [!hurd-i386], libjpeg-dev, libltdl3-dev, - libsystemd-dev [linux-any], libtiff-dev, libusb-1.0-0-dev [!hurd-i386], pkg-config, diff -Nru sane-backends-1.0.25/debian/rules sane-backends-1.0.25/debian/rules --- sane-backends-1.0.25/debian/rules 2017-05-21 10:04:48.0 +0200 +++ sane-backends-1.0.25/debian/rules 2017-05-29 13:24:34.0 +0200 @@ -29,7 +29,7 @@ endif %: - dh $@ --parallel --with autotools_dev,systemd + dh $@ --parallel --with autotools_dev override_dh_auto_configure: autoconf @@ -130,9 +130,6 @@ override_dh_installinit-arch: dh_installinit -psane-utils --name=saned -override_dh_systemd_enable-arch: - dh_systemd_enable --no-enable saned.socket - override_dh_strip-arch: dh_strip --dbg-package=libsane-dbg diff -Nru sane-backends-1.0.25/debian/sane-utils.install sane-backends-1.0.25/debian/sane-utils.install --- sane-backends-1.0.25/debian/sane-utils.install 2017-05-21 10:04:48.0 +0200 +++ sane-backends-1.0.25/debian/sane-utils.install 2017-05-29 13:24:22.0 +0200 @@ -8,5 +8,3 @@ usr/share/man/man1/scanimage.1 usr/share/man/man8/saned.8 tools/umax_pp usr/bin -debian/saned.socket lib/systemd/system -debian/saned@.service lib/systemd/system ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] scanner dependencies
On Mon, May 29, 2017 at 01:55:51PM +0200, Adam Borowski wrote: > On Mon, May 29, 2017 at 08:16:28PM +0900, Olaf Meeuwissen wrote: > > Florian Zieboll writes: > > > IIRC, a sane developer had replied to that thread and said > > > that also saned just checks for the existence of libsystemd0 but does > > > not need it at all. So the "dependency" is null and could be removed. > > > > You remember correctly ;-) > > > > It's not a "dependency", it's a compile-time option. To get rid of the > > Depends:, you will need to drop libsystemd-dev (and maybe dh-systemd) > > from the debian/control file and rebuild the package. That's all. > > Which actually are (Build-)Dependencies, that turn into actual Dependencies > once built. But indeed, like for the vast majority of infested packages, > it's all it takes -- most upstream developers are not evil, and DTRT when > systemd headers are not available. Even if they're systemd apologists > themselves, many projects want to work on BSD and so on. > > A debdiff attached, compile-tested only (I have no scanner hardware). Sounds like sonething that should go into Devuan jessie as a bug fix. After someone tests it, of course. -- hendrik > diff -Nru sane-backends-1.0.25/debian/changelog > sane-backends-1.0.25/debian/changelog > --- sane-backends-1.0.25/debian/changelog 2017-05-21 10:04:48.0 > +0200 > +++ sane-backends-1.0.25/debian/changelog 2017-05-29 13:24:39.0 > +0200 > @@ -1,3 +1,10 @@ > +sane-backends (1.0.25-4.1.0nosystemd1) unstable; urgency=medium > + > + * Non-maintainer upload. > + * Cure systemd infestation. > + > + -- Adam Borowski Mon, 29 May 2017 13:24:39 +0200 > + > sane-backends (1.0.25-4.1) unstable; urgency=medium > >* Non-maintainer upload. > diff -Nru sane-backends-1.0.25/debian/control > sane-backends-1.0.25/debian/control > --- sane-backends-1.0.25/debian/control 2017-05-21 10:04:48.0 > +0200 > +++ sane-backends-1.0.25/debian/control 2017-05-29 13:23:16.0 > +0200 > @@ -8,7 +8,6 @@ > autoconf, > chrpath, > debhelper (>= 10), > - dh-systemd, > gettext, > libavahi-client-dev, > libcam-dev [kfreebsd-any], > @@ -17,7 +16,6 @@ > libieee1284-3-dev [!hurd-i386], > libjpeg-dev, > libltdl3-dev, > - libsystemd-dev [linux-any], > libtiff-dev, > libusb-1.0-0-dev [!hurd-i386], > pkg-config, > diff -Nru sane-backends-1.0.25/debian/rules sane-backends-1.0.25/debian/rules > --- sane-backends-1.0.25/debian/rules 2017-05-21 10:04:48.0 +0200 > +++ sane-backends-1.0.25/debian/rules 2017-05-29 13:24:34.0 +0200 > @@ -29,7 +29,7 @@ > endif > > %: > - dh $@ --parallel --with autotools_dev,systemd > + dh $@ --parallel --with autotools_dev > > override_dh_auto_configure: > autoconf > @@ -130,9 +130,6 @@ > override_dh_installinit-arch: > dh_installinit -psane-utils --name=saned > > -override_dh_systemd_enable-arch: > - dh_systemd_enable --no-enable saned.socket > - > override_dh_strip-arch: > dh_strip --dbg-package=libsane-dbg > > diff -Nru sane-backends-1.0.25/debian/sane-utils.install > sane-backends-1.0.25/debian/sane-utils.install > --- sane-backends-1.0.25/debian/sane-utils.install2017-05-21 > 10:04:48.0 +0200 > +++ sane-backends-1.0.25/debian/sane-utils.install2017-05-29 > 13:24:22.0 +0200 > @@ -8,5 +8,3 @@ > usr/share/man/man1/scanimage.1 > usr/share/man/man8/saned.8 > tools/umax_pp usr/bin > -debian/saned.socket lib/systemd/system > -debian/saned@.service lib/systemd/system > ___ > 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] scanner dependencies
Hendrik Boom writes: Sounds like sonething that should go into Devuan jessie as a bug fix. After someone tests it, of course. "Of course"... Which would you rather have, an untested fix or a known bug? IMNSHO that's an insidious question and neither a yes or a no is "of course" correct. Arnt ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Bash keyboard shortcuts working really ugly [SOLVED]
On 170526-14:52+0200, Alessandro Selli wrote:
> On Thu, 25 May 2017 at 07:30:29 +
> Miroslav Rovis wrote:
>
> > On 170525-06:51+0200, Alessandro Selli wrote:
> > > On Wed, 24 May 2017 at 16:27:36 + Miroslav Rovis
> > > wrote:
> > >
[NOTE: ... typos in the old quoted texts below edited for readability
('s/demonstate/demonstrate/' in two pastes of mine, also 's/undr/under/' in
Alessandro's reply) ]
The Issue
=
> > > > mr@gd0v:~$ I am only trying to demonstrate the issue.
> > > >
> > > > That's ' I' in first editable space of the command line. I move to
> > > > beginning with Ctrl-A.
> > > >
> > > > And I press Alt-D. Here's what I get:
> > > >
> > > > mr@gd0v:~$ รค I am only trying to demonstrate the issue.
> > > >
> > > > But I did press Alt-D... So that one doesn't work.
> > ...
Alessandro's reply which solved it for me:
> > > This is a problem with Xresources if it happens under Xorg, and/or with
> > > input library keybindings, that is with the .inputrc file.
> > >
[NOTE: Let's make the solution conspicuously stand out, for people who will be
getting here via search engines with the problem like mine: ]
> > > Under X I can replicate your problem when I comment this line in
> > > ~/.Xresources:
> > >
> > > *metaSendsEscape: true
=
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
| | | | | | | | | | | | | | |
> > >
> > > Try uncommenting or adding this line, then run:
> > >
> > > xrdb -merge ~/.Xresources
> > >
> > > open a new terminal and see if the problem went away.
> >
> > #==#
> > # And it did go away! Both Alt-D and Alt-Backspace now work! #
> > #==#
>
That's all. Now follows my belated reply to Alessandro's kind email. It is
belated because I hadn't secured sufficiently well my Devuan to be able to use
it more freely until a few hours ago.
Being it very likely a fact that my Gentoo has been broken into[1] again
(mildly so, but yes: broken into, IMO), notwithstanding and regardless of my
serious and stubborn effort to not be owned again[2]), I decided to take
security even more seriously[3] with my main OS of the next months to come,
Devuan.
Because I want my Devuan to endure any hardship and to last for me, and that I
be able to do good things with it :) .
Alessandro pls. accept my apologies for being this late. In truth I got
hundreds of emails (from all kinds of GNU/FOSS/... lists that I'm subscribed
to) today with remarkably (so far) well working Getmail, Maildrop and Mutt, as
well as Postfix --for sending only--, along with for local mail... Hundreds of
emails because since my reply to Steve which I sent just some twenty minutes
after I replied to you, I haven't gone online with my Devuan, since four days
ago, until today. I really want to make my Devuan secure.
> /me pops open a bottle of Spumante and toast!
My toast to you too, but the red Italian wine you mention further below sounds
even more delicious!
>
> > And just think of it: I was willing (almost ready) to reinstall my Devuan
> > because of this trivial glitch, kind of... Phew!
>
> It's trivial *after* you learned what the issue was, but it can drive you
> crazy for weeks before that! Especially when the issue concerns some of
> those arcane, scantly documented old-time Unix config files and settings very
> few people think of when something misbehaves under X.
> I am not sure this setting, that is, everything you put in your
> ~/.Xresources file, is read automatically at every X session, though I
> believe it probably is: it depends by your Desktop Manager. In my Devuan
> system I find it configures in /etc/X11/Xsession, where I can find:
(Looking into):
> #!/bin/sh
> #
> # /etc/X11/Xsession
> #
> # global Xsession file -- used by display managers and xinit (startx)
>
> [...]
>
> USRRESOURCES=$HOME/.Xresources
>
> and then in /etc/X11/Xsession.d/30x11-common_xresources:
>
> # $Id: 30x11-common_xresources 305 2005-07-03 18:51:43Z dnusinow $
>
> # This file is sourced by Xsession(5), not executed.
>
> [...]
>
> if has_option allow-user-resources && [ -f "$USRRESOURCES" ]; then
> if type xrdb >/dev/null 2>&1; then
> xrdb -merge $USRRESOURCES
> else
I found both the files, and they, by quick check, have the same content you
cite in my box as well, but I only vaguely understand what they do...
>
> [...]
>
> > But that's what the developers are here for us users/hopeful testers...
>
> Surely!
>
> By the way, people: as I was perusing among the files in /etc/X11
> documenting this email of mine, I updated this file:
>
> --- /etc/X11/wdm/Xresources 2017-05-26 14:12:25.104413649 +0200
> +++ /etc/X11/wdm/Xresources.orig2017-05-26 14:22:20.487768651 +0200
> @@ -8,8 +8,7 @@
> CtrlReturn: set-session-argument(failsafe) finish-field()\n\
> Return: set-session-argument() finish-field(
[DNG] installation of Jessie 1.0 fails (busybox)
With Jessie 1.0 out, I decided to move from the beta as a system to play with to make Jessie 1.0 my primary system. I dd copied the DVD ISO to a 8 G USB key and booted it. I didn't expect to have any installation (expert) problems, but did. After having the partitioner format all partitions, I began to install the new base system. This proceeded for a while. I chose the 3.16.0-4-amd64 kernel. Then installation of base system halted with the error: "An error was returned when trying to install the busybox package onto the target system." It suggested taking a look at syslog, but it was not informative. Immediately after it says klogd is installed, it says "syslogd started: BusyBox v1.22.1" Searching on line did not help. Could there be a problem with the ISO? If so, would it be best to download it anew or should I simply recopy it to the key? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
