Processing of pev_0.81-1_source.changes

2021-01-19 Thread Debian FTP Masters 
pev_0.81-1_source.changes uploaded successfully to localhost
along with the files:
  pev_0.81-1.dsc
  pev_0.81.orig.tar.gz
  pev_0.81-1.debian.tar.xz
  pev_0.81-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

pev_0.81-1_source.changes ACCEPTED into experimental

2021-01-19 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Jan 2021 09:39:20 +0100
Source: pev
Architecture: source
Version: 0.81-1
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Petter Reinholdtsen 
Changes:
 pev (0.81-1) experimental; urgency=medium
 .
   * QA upload.
 .
   * New upstream version 0.81.
 - Dropped 10-bogus-const.patch, 11-pehash-openssl-1.1.patch,
   11-pesec-openssl-1.1.patch and 12-text-typos.patch as the issues
   are fixed upstream.
 - Dropped 01-plugins-path.patch and moved setting to d/rules, as
   the upstream code provide global define for it now.
Checksums-Sha1:
 567c2bfe74ca520c5bf99bf90ce3a3d1ece9fa0b 1829 pev_0.81-1.dsc
 f5d3aedeefbcab108d7fc5d65fddf0576bf43b41 676143 pev_0.81.orig.tar.gz
 62fd985b160ab5488cee1ce2352444fcc21d2ec1 3688 pev_0.81-1.debian.tar.xz
 199dc017f94dc9d74c4b27025edad602fcab2987 6426 pev_0.81-1_source.buildinfo
Checksums-Sha256:
 95c1071ab4238eaeebd3241340f60a477ad5a43eac04decba5ce12341f49a901 1829 
pev_0.81-1.dsc
 4192691c57eec760e752d3d9eca2a1322bfe8003cfc210e5a6b52fca94d5172b 676143 
pev_0.81.orig.tar.gz
 f7b02026df10db1279c0dc48bb126dd84726fdb3316563ec86aefdadf035b6cf 3688 
pev_0.81-1.debian.tar.xz
 35b6dd23ff4f4e14fe211b34166ac2144a550965fb9f839a2c29e46c60394868 6426 
pev_0.81-1_source.buildinfo
Files:
 12f04806faf36e11c115942d6a0b489f 1829 utils optional pev_0.81-1.dsc
 9800200f26adadf4812919ae02971476 676143 utils optional pev_0.81.orig.tar.gz
 73cda18d8dbea49505a14b69589c7224 3688 utils optional pev_0.81-1.debian.tar.xz
 76b4597705062f57379b856da0af3499 6426 utils optional 
pev_0.81-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmAGnOsACgkQgSgKoIe6
+w6E8hAAizbC88WgcqRmACaVjSaKriOKx+LTRb1bgaeJ4YvkdtrXLFtTEDv/y33x
UwAcB/JS8uYVMmmTjbpq/AF1VYJfE9MNksjPXYF1jvj4AD694EeBBHe2Z0OG06rY
w5Mwe8t9rcgmGb061aDXIdHOotgtqj1CtOggwlBs86eN52SgN5kKnQIly2k+ywme
3MeQqXnLSVwx/gLbFZ35vgGfceQKJ0D010E8dW42dQ/ruCbhjo1hRsvmfVfX43DX
RUzfqBZWZzksWGn6gLL+030rT4LSJkft60qj8oS8jtv6syTKT42XCQPFdUe1T1y/
ixGPCagQ2Z3LPeYN6oUC5BFuJ6NWcY20m0VRwD4iV9a+Ual4guiS50uw+IXpyoSo
Lwmphvz6a5E2agwFLHqXg/21ZRxWpKJGeC3PaaHyYldt0bq0asy2gDZL2qciaZgg
AgQbjR800swrsEeIdMS4O6ZCBVl5xURTp0M6rGvgwlci5oHeTpkjRiKfC2LPuPCW
AsPrAHfzkUoXTihfuLPfBboLO8E3ngbvhPeRYFS2Rdw2RZgl0WYEj/1raFWEFRf9
WJzteI7qimzWvR6XRzBpXhKWZqvHKSZtyVlL+u10hW08CqMa3vQsucsoxtyxjrT2
iWqF3I7R38kMOgGrM9M8q/FTvIq9yikIMMtzQXBBMdl4IekRK0c=
=ivhQ
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

schroot mounting directory from host

2021-01-19 Thread jffry 

Hi schroot maintainers!

I'm trying to debug a change in imagemagick which is causing gscan2pdf 
tests to fails, thereby preventing imagemagick 8:6.9.11.57+dfsg-1 from 
migrating to testing:


https://qa.debian.org/excuses.php?package=imagemagick

Up to now, I have just been using schroot via sbuild to build gscan2pdf 
in a clean chroot before uploading. I've also seen that I can launch 
schroot interactively, but that (understandably by default) seems to 
have no access to the host, but it would be much more comfortable to 
mount the host directory where I am debugging the package so that I can 
see the directory in both the the chroot and the host.


How can I achieve this on a case by case basis?

Thanks and regards

Jeff Ratcliffe

Re: schroot mounting directory from host

2021-01-19 Thread Roger Leigh 
On 19 Jan 2021, at 15:56, jf...@posteo.net wrote:
> 
> I've also seen that I can launch schroot interactively, but that 
> (understandably by default) seems to have no access to the host, but it would 
> be much more comfortable to mount the host directory where I am debugging the 
> package so that I can see the directory in both the the chroot and the host.

Hi Jeff,

This is a standard schroot feature—enable a bind mount in the schroot 
configuration.  Look at the different “profiles” in /etc/schroot.  You’ll see 
bind mounting used for the “desktop” profile.  You’ll want to copy that for the 
“sbuild”/“buildd” profile in use with your sbuild commands.  Add a bind mount 
for the build directory, and you should be able to see the same location on 
both the host and in the chroot.

You can have multiple “profiles” and multiple chroot configurations.  You could 
create different ones for use with sbuild, and choose the one you want when 
running sbuild.

That said, the chroot should be directly accessible to you from the host 
system, so shouldn’t be strictly necessary.  Depends on the setup, but it 
should be under /var/lib/schroot/session or similar.  Run "schroot -i" and it 
will tell you the “mount location” on the host system.  You might need to be 
root to access it, but it shouldn’t require any configuration changes.

Regards,
Roger

Processing of xine-ui_0.99.9-2_source.changes

2021-01-19 Thread Debian FTP Masters 
xine-ui_0.99.9-2_source.changes uploaded successfully to localhost
along with the files:
  xine-ui_0.99.9-2.dsc
  xine-ui_0.99.9-2.debian.tar.xz
  xine-ui_0.99.9-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

xine-ui_0.99.9-2_source.changes ACCEPTED into unstable

2021-01-19 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Jan 2021 20:08:24 +0100
Source: xine-ui
Architecture: source
Version: 0.99.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 583128 881790 907268 965895
Changes:
 xine-ui (0.99.9-2) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * QA upload.
   * Set Maintainer to Debian QA Group.  (See: #881516)
   * Import packaging history into GIT.
   * Set Rules-Requires-Root: no.
   * Switch to debhelper-compat (= 13).  (Closes: #965895)
   * Convert d/rules to use dh.  (Closes: #881790, #583128)
   * Enable more hardening.
   * Bump watch file version to 4.
   * Convert documentation to UTF-8.
   * Fix typos found by lintian.
   * Bump Standards-Version to 4.5.1.
 .
   [ Kees Cook ]
   * Fix LIRC detection (Closes: #907268):
 - m4/_xine.m4: Update lirc pkg-config name.
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Set upstream metadata fields: Archive, Repository.
   * Fix day-of-week for changelog entry 0.9.8-2.
Checksums-Sha1:
 a77b6cbea8f0440af7f5cbb24a485140d94878eb 2216 xine-ui_0.99.9-2.dsc
 99972a03861fedfcfef0bb8cf9164868a3bf6861 12132 xine-ui_0.99.9-2.debian.tar.xz
 78292af6de36bc9d7635b3ec204a1cccfae47a44 8592 xine-ui_0.99.9-2_source.buildinfo
Checksums-Sha256:
 5270c86bac4009e674f1ecd19be3ba39573ebec73b16b81f2d94116d3f11067b 2216 
xine-ui_0.99.9-2.dsc
 95a1401410cb0f977462bf2ce7d51dee3c80645497e6eea63889d0a0a26a513d 12132 
xine-ui_0.99.9-2.debian.tar.xz
 2db94256c10e68aa971957abfea1c39ad6db9b588c41c1bdf360a147e449280a 8592 
xine-ui_0.99.9-2_source.buildinfo
Files:
 c03751ced3968587493ba25082e0d7e5 2216 video optional xine-ui_0.99.9-2.dsc
 37a79540c91d4553c71553ea2780c26b 12132 video optional 
xine-ui_0.99.9-2.debian.tar.xz
 0cd558c65dda085809589b12742d0b15 8592 video optional 
xine-ui_0.99.9-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmAHLuQQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCGKBD/9VpakXP8657/CmpEj4ZMivOwPpheeDWEy2
mvfzmJKwCsFBfXysDcazU7tZr6YQpfKn7u3HDJSHSBUDdeqL3AVAwZ5i6TM3rav8
oN5Zc0miPQ2GL42aOaa3Dfv5idB4z9GURrnSnJ6hLOzgEumoVlvh5gvhrglf5bkN
MSzupP87DhQi58fG9qOR6wA6Px9YXZjIXqgi5OpHofPSBdrfF5XYRv3ZSvtNPkBh
ghLysF02ge22jYjcxbBnaE04I7/T5TbTJHMHAMbNxrklRxHLXDXyn3tpQFSi184m
Da0I8Qi9/GGfkGY8AWHfjR9hsnIwHjPAYq87Drh4bxA/yM4I0c0mnsq1Pgb4FGhu
+HrfzRLDKy+6Jg59JL/NiDB7Iq5uUP0gnH8PgaKvk0QtcZdKsFI6pHc44Mp4kC5d
zFBdlGprvnT5osIaFtpVFfHv/aj3bHo+GQSWbumNM7ciYisfDlPgPIy9khzzlVf8
oHVJTUa7+ENO8Zn/3JJLrBnVgfnJNWgcA1qcLMUa5SnlmL1TAIScKjT95rxlZZTC
M9JDsQeHTpRZveSL6ZkLKtrcWcXjHdGnxQqckxFjiC7p9liHH0bq4226D+LGwtTW
VDOskHn61X++kib9rw0y6UnzB1AgBiL9VyWTJFCSM9sW5eQ4r/EoUtscvWa8EVbt
vhENpKqbpA==
=xaq9
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#646247: marked as done ([libinklevel5] requires deprecated usblp devices for USB printers ("Could not access '/dev/usb/lp0' or '/dev/usblp0'."))

2021-01-19 Thread Debian Bug Tracking System 
Your message dated Tue, 19 Jan 2021 21:23:59 -0500
with message-id <16e3495d2b9ad7c8e8c36f023adb668927bfed4c.ca...@debian.org>
and subject line Re: [libinklevel5] requires deprecated usblp devices for USB 
printers ("Could not access '/dev/usb/lp0' or '/dev/usblp0'.")
has caused the Debian Bug report #646247,
regarding [libinklevel5] requires deprecated usblp devices for USB printers 
("Could not access '/dev/usb/lp0' or '/dev/usblp0'.")
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
646247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: libinklevel5
Version: 0.8.0-1.1+b1
Severity: serious

libinklevel requires /dev/usb/lp? or /dev/usblp? for USB printers. 
Otherwise, it returns DEV_USB_LP_INACCESSIBLE:



 case DEV_USB_LP_INACCESSIBLE:
   printf("Could not access '/dev/usb/lp%d' or '/dev/usblp%d'.\n",
  portnumber, portnumber);
   break;


get_device_id() contains:


 if (port == USB) {
   sprintf(device_file1, "/dev/usb/lp%d", portnumber);
   sprintf(device_file2, "/dev/usblp%d", portnumber);
   fd = open(device_file1, O_RDONLY);
   if (fd == -1) {
 fd = open(device_file2, O_RDONLY);
   }
   if (fd == -1) {
 return DEV_USB_LP_INACCESSIBLE;
   }
 }


Therefore, polling ink levels on USB printers fails if the usblp LKM is 
not loaded:



$ ink -p usb
Could not access '/dev/usb/lp0' or '/dev/usblp0'.
Could not get ink level.
chealer@vinci:~$


Both ink and Qink fail with USB printers. qink just complains "Printer 
error No printers detected on this system". Launching it as root won't 
help. However, printing works...


usblp used to be loaded when a USB printer was plugged in. usblp is now 
blacklisted by cups, since CUPS switched from usblp to libusb:



Drop usb-backend-both-usblp-and-libusb.dpatch. It's causing crashes, and
  upstream does not want it either. Instead, add a blacklist file
  debian/local/blacklist-cups-usblp.patch and install it into
  /etc/modprobe.d/; that way, we don't require kernels to disable usblp, and
  allow other spoolers than cups to work.

http://packages.debian.org/changelogs/pool/main/c/cups/current/changelog#version1.4.6-8


# cat /etc/modprobe.d/blacklist-cups-usblp.conf
# cups talks to the raw USB devices, so we need to blacklist usblp to 
avoid

# grabbing them
blacklist usblp
root@vinci:/etc#


A workaround is to purge cups, or to manually load usblp.

This means that ink and Qink won't just work for the vast majority of 
printers.


--- System information. ---
Architecture: i386
Kernel: Linux 3.0.0-2-amd64

Debian Release: wheezy/sid
990 testing security.debian.org
990 testing ftp.ca.debian.org
500 unstable ftp.ca.debian.org
1 experimental ftp.ca.debian.org

--- Package information. ---
Depends (Version) | Installed
-+-===
libc6 (>= 2.3) | 2.13-21
libieee1284-3 | 0.2.11-10


Package's Recommends field is empty.

Package's Suggests field is empty.





--- End Message ---
--- Begin Message ---
Version: 0.9.2-1

According to upstream libinklevel maintainer, libinklevel 0.9.0 or later is
using libusb instead of deprecated device nodes. I believe this should no
longer be an issue with newer libinklevel packages.

Thanks,
Boyuan Yang

On Sat, 22 Oct 2011 12:36:17 -0400 Filipus Klutiero  wrote:
> Package: libinklevel5
> Version: 0.8.0-1.1+b1
> Severity: serious
> 
> libinklevel requires /dev/usb/lp? or /dev/usblp? for USB printers. 
> Otherwise, it returns DEV_USB_LP_INACCESSIBLE:
> 
> >  case DEV_USB_LP_INACCESSIBLE:
> >    printf("Could not access '/dev/usb/lp%d' or '/dev/usblp%d'.\n",
> >   portnumber, portnumber);
> >    break;
> 
> get_device_id() contains:
> 
> >  if (port == USB) {
> >    sprintf(device_file1, "/dev/usb/lp%d", portnumber);
> >    sprintf(device_file2, "/dev/usblp%d", portnumber);
> >    fd = open(device_file1, O_RDONLY);
> >    if (fd == -1) {
> >  fd = open(device_file2, O_RDONLY);
> >    }
> >    if (fd == -1) {
> >  return DEV_USB_LP_INACCESSIBLE;
> >    }
> >  }
> 
> Therefore, polling ink levels on USB printers fails if the usblp LKM is 
> not loaded:
> 
> > $ ink -p usb
> > Could not access '/dev/usb/lp0' or '/dev/usblp0'.
> > Could not get ink level.
> > chealer@vinci:~$
> 
> Both ink and Qink fail with USB printers. qink just complains "Printer 
> error No printers detected on this system". Launching it as root won't 
> help. However, printing works...
>