date:20150114

Bug#775338: gtk3-engines-oxygen: Themed gtk3 apps drop down boxes do not work properly

2015-01-14 Thread Dmitry Smirnov

On Thu, 15 Jan 2015 02:25:46 kittyofthebox wrote:
 it's quite
 simple this theme engine breaks drop down menus for me in gtk3 applications

How exactly drop down lists are broken?


 and other themes 

How do you change themes? Using kde-config-gtk-style?


 do not and it has been doing this a long time for me on
 two different laptops and for some of my friends.

Then maybe you could find which package upgrade broke it?


 I can't give precise steps on reproduction
 because I have no where to start besides This doesn't work right and
 hasn't for awhile

I reckon I might be doing something wrong because it works for me. :)
You have to be more specific or I'm not sure if I can help...

-- 
All the best,
 Dmitry Smirnov


signature.asc
Description: This is a digitally signed message part.

Bug#746219: Retitle

2015-01-14 Thread Mathieu Parent

COntrol: retitle -1 ITP: php-pam -- PAM integration


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#774765: Retitle according to source name

2015-01-14 Thread Mathieu Parent

Control: retitle -1 ITP php-oci8 -- Extension for Oracle Database

and not binary name.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#775367: libpgm-dev: broken .so symlink

2015-01-14 Thread Bernd Zeimetz

Package: libpgm-dev
Version: 5.1.118-1~dfsg-1
Severity: important

libpgm-dev ships a broken symlink:

root@think:~# ls -la /usr/lib/libpgm-5.1.so
lrwxrwxrwx 1 root root 16 Oct 20 22:47 /usr/lib/libpgm-5.1.so - 
/libpgm-5.1.so.0

as libpgm-5.1.so doesn't seem to be used by pkg-config and friends I
think important is a high enough severity.


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpgm-dev depends on:
ii  libpgm-5.1-0  5.1.118-1~dfsg-1

libpgm-dev recommends no packages.

libpgm-dev suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#774930: htop shows IORW. Man page says IO

2015-01-14 Thread alberto fuentes

On Wed, Jan 14, 2015 at 8:32 PM, Eugene V. Lyubimkin
 In htop output columns, I have exactly 'IORR' and 'IOWR'.

 Could you please elaborate where did you see 'IORW'?

If you add the IO_RATE it shows as IORW. I attach capture

Bug#775375: python-django: CVE-2015-0219 CVE-2015-0220 CVE-2015-0221 CVE-2015-0222

2015-01-14 Thread Salvatore Bonaccorso

Source: python-django
Version: 1.7.1-1
Severity: grave
Tags: security upstream fixed-upstream

Hi,

the following vulnerabilities were published for python-django.

CVE-2015-0219[0]:
WSGI header spoofing via underscore/dash conflation

CVE-2015-0220[1]:
Mitigated possible XSS attack via user-supplied redirect URLs

CVE-2015-0221[2]:
Denial-of-service attack against django.views.static.serve

CVE-2015-0222[3]:
Database denial-of-service with ModelMultipleChoiceField

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities  Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-0219
[1] https://security-tracker.debian.org/tracker/CVE-2015-0220
[2] https://security-tracker.debian.org/tracker/CVE-2015-0221
[3] https://security-tracker.debian.org/tracker/CVE-2015-0222
[4] https://www.djangoproject.com/weblog/2015/jan/13/security/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773319: pre-approval: unblock: sudo/1.8.10p3-1.1; possibly sudo/1.8.11p2-1.1?

2015-01-14 Thread Ivo De Decker

Control: tags -1 moreinfo

Hi,

On Tue, Dec 16, 2014 at 10:02:55PM +0100, Christian Kastner wrote:

(rearranging the original mail a bit)

 controversial
 Furthermore, I was wondering though whether you'd consider allowing
 sudo/1.8.11p2 from unstable to migrate.
 
 The diff between testing and unstable is huge (MBs), so this would be
 very difficult to review and of course totally against freeze policy.
 However, I am under the impression that
 
   (a) it would be highly preferrable to support 1.8.11p2 in Jessie,
   especially from a security POV
 
   (b) According to [2,3,4], most of the changes are bugfixes. In fact,
   I only count 7 non-fix changes and non-translation changes,
   and most of the fix changes appear to be highly desirable.
 
 Furthermore, the largest part of this code base, [3], has unstable since
 2014-10-10, and its migration to testing was only interrupted by the
 upload of revision -2 of [3] on 2014-10-20, so apparently juuust not
 enough for the full 10-day period. This upload merely added two patches.
 
 Then again, on 2014-10-30, [4] was uploaded. This new upstream release
 contained only a single (apparently urgent) bugfix. However, this upload
 reset the 10-day clock again, so 1.8.11p* did not enter testing again.
 
 So there really isn't anything that new to Debian in the version in
 unstable. Looking back, the easiest solution would probably have been to
 ask for an unblock of [4] (the one-change fix) just after its upload on
 2014-10-30, but that's water under the bridge now.
 /controversial

It baffles me that the maintainer showed such a blatant disregard for the
freeze policy. 1.8.11p1 could have migrated easily in October if the
maintainer paid even the slightest bit of attention.

 If allowing 1.8.11p2 to migrate is something you'd consider discussing,
 please let me know how I can help in your deliberations. 

Obviously it isn't going to be unblocked now.


 simple
 Based on a patch provided by upstream, I created a debdiff (attached)
 for 1.8.10p3 in testing with the following changelog entry:
 
  * Backport upstream's fix for host specifications using a FQDN.
These were no longer working since 1.8.8. Closes: #731583
 
 Considering that the severity of #731583 is serious, I assume an upload
 to t-p-u should be OK?
 /simple

I'm reluctant to allow this, as this essentially means dumping this new
version into jessie untested. I would prefer if it was just uploaded to
unstable (reverting the new upstream version there), to allow it to be tested
there, and migrate to jessie that way. If there is a good reason why this
isn't possible (if it introduces other issues in unstable by doing this),
please explain why and I'll consider allowing a t-p-u upload.

Please remove the moreinfo tag when you add info to this bug.

 If this change
 is simply too big, please let me know if you are OK with the t-p-u
 upload of the attached debdiff for 1.8.10p3, and I will then contact the
 maintainer / look for NMU sponsorship.

Cheers,

Ivo


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721760: Find a way for people without an account in LDAP to authenticate to the site

2015-01-14 Thread Jonathan Wiltshire (Front Desk)

Control: tag -1 moreinfo

Hi Enrico,

On Tue, Sep 03, 2013 at 10:06:01PM +0200, Enrico Zini wrote:
 we could use a way for non-DDs to authenticate to the site, 
 
 That could allow applicants to edit their own information, as well as to
 apply for DD, DM, collab-maint, guest accounts and whatever we are going
 to implement.
 
 There is the idea of having Alioth as a backend for DACS: that would
 solve the problem nicely, since everyone can create an Alioth account.
 
 I'm creating this ticket to track progress on this.

Non-DDs can authenticate with an Alioth login; shall I close this bug?

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#775304: openntpd does not include ntpctl

2015-01-14 Thread Dererk

On 13/01/15 18:28, Brian Minton wrote:
 Package: openntpd
 Version: 20080406p-10
 Severity: normal

 Dear Maintainer,

 The ntp package includes ntpdc and ntpq, among other utilities, for
 querying the server.  However, the openntpd package doesn't include the
 ntpctl utility, as documented at http://www.openntpd.org/manual.html
 (and in addition, doesn't seem to create the runtime socket that ntpctl
 would use at /var/run/ntpd.sock).

Hi BrianMinton!

I'm not sure if this is by chance or not, but the utility you are
referring to is available just at a newer version of openntpd, which,
coincidentally, we have been coordinating at upstream for a mayor
package port and patch refresh.

This action took place a few weeks ago and a huge software upgrade is
going to see daylight at Debian archive pretty soon, currently its just
on experimental due to some mayor changes on the driftfile and several
other patches I've been unable to confirm yet that might break backwards
compatibility at upgrade-time.

I'll be closing with the experimental upload pretty soon.


Cheers,

Dererk

-- 
BOFH excuse #367:

Webmasters kidnapped by evil cult.




signature.asc
Description: OpenPGP digital signature

Bug#775370: libegl1-mesa-drivers: Version 10.4.2-1 has no Multi Arch (i386/amd64) support

2015-01-14 Thread Gabriel Mainberger

Package: libegl1-mesa-drivers
Version: 10.4.2-1
Severity: important
Tags: newcomer

The current version 10.4.2-1 of the libegl1-mesa-drivers, does not have multi
arch support. On multi arch systems i386/amd64 this produces this error (sorry,
it is in german):

Fehler traten auf beim Bearbeiten von:
 /home/gabriel/Downloads/libegl1-mesa-drivers_10.4.2-1_i386.deb
andromeda:/var/cache/apt/archives# dpkg -i /home/gabriel/Downloads/libegl1
-mesa-drivers_10.4.2-1_i386.deb libegl1-mesa-drivers_10.4.2-1_amd64.deb
dpkg: Fehler beim Bearbeiten des Archivs /home/gabriel/Downloads/libegl1-mesa-
drivers_10.4.2-1_i386.deb (--install):
 libegl1-mesa-drivers:i386 10.4.2-1 (Multi-Arch: no) kann nicht zusammen mit
libegl1-mesa-drivers installiert werden, welches mehrere installierte Instanzen
hat
dpkg: Fehler beim Bearbeiten des Archivs libegl1-mesa-
drivers_10.4.2-1_amd64.deb (--install):
 libegl1-mesa-drivers:amd64 10.4.2-1 (Multi-Arch: no) kann nicht zusammen mit
libegl1-mesa-drivers installiert werden, welches mehrere installierte Instanzen
hat
Fehler traten auf beim Bearbeiten von:
 /home/gabriel/Downloads/libegl1-mesa-drivers_10.4.2-1_i386.deb
 libegl1-mesa-drivers_10.4.2-1_amd64.deb

As it is an traditional package, shouldn't it be removed automatcally?

system:# apt-get remove --purge libegl1-mesa-drivers

After a manual remove, everything is fine.



-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_CH.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libegl1-mesa-drivers depends on:
ii  libc6 2.19-13
ii  libdrm-nouveau2   2.4.58-2
ii  libdrm-radeon12.4.58-2
ii  libdrm2   2.4.58-2
ii  libegl1-mesa  10.4.2-1
ii  libelf1   0.159-4
ii  libffi6   3.1-2+b2
ii  libgbm1   10.4.2-1
ii  libgcc1   1:4.9.2-10
ii  libgl1-mesa-dri   10.4.2-1
ii  libglapi-mesa 10.4.2-1
pn  libllvm3.3none
ii  libopenvg1-mesa [libopenvg1]  10.3.2-1
ii  libstdc++64.9.2-10
ii  libudev1  215-9
ii  libwayland-client01.6.0-2
ii  libwayland-server01.6.0-2
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  multiarch-support 2.19-13

libegl1-mesa-drivers recommends no packages.

libegl1-mesa-drivers suggests no packages.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#775256: unblock (pre-approval): mate-session-manager/1.8.1-6

2015-01-14 Thread Ivo De Decker

Control: tags -1 confirmed moreinfo

Hi,

On Tue, Jan 13, 2015 at 10:46:43AM +0100, Mike Gabriel wrote:
 Please consider unblocking planned upload of package mate-session-manager

Please go ahead.

Cheers,

Ivo


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#775352: unblock (pre-approval or jessie-p-u): autopkgtest (was Fixing autopkgtest RC bug #775076 via t-p-u)

2015-01-14 Thread Ivo De Decker

Control: tags -1 confirmed moreinfo

Hi,

On Wed, Jan 14, 2015 at 01:57:33PM -0200, Antonio Terceiro wrote:
Opening a bug report since that's way more likely to be handled in this
way.

Thanks for that.

On Sun, Jan 11, 2015 at 02:00:45PM +0100, Martin Pitt wrote:
Hello release team,

Christian Kastner discovered that when using vmdebootstrap with
autopkgtest's VM setup script it erroneously enables dpkg's
force-unsafe-io option on the host instead of the guest. This can
lead to potential system damage and thus should qualify as RC:

https://bugs.debian.org/775076

This is fixed in version 3.9.3 in unstable now, including a postinst
cleanup for cleaning up an erroneously created
/etc/dpkg/dpkg.cfg.d/autopkgtest on the host.

At the time when testing froze, testing had 3.6, and unstable's 3.7
(with a lot of changes) was one day short of propagating to testing;
so as these were already out of sync, I just kept on uploading to
unstable as that's what most people use for development. So I prepared
a debdiff for testing-proposed-updates at

https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=34;filename=autopkgtest.775076.jessie.debdiff;att=1;bug=775076

We prefer patches attached to the bug instead of links to somewhere else.

Anyway, please go ahead with the upload to jessie (the distribution should
also be set to 'jessie') and remove the moreinfo tag from this bug once the
upload is accepted into t-p-u.

autopkgtest is mostly a Debian/Ubuntu developer, QA, and continuous
integration tool, so honestly the testing version isn't that
interesting any more. So if you prefer, I'd be perfectly okay (and
in fact happier) with getting 3.9.3 into testing instead; it has a lot
of new features, but also a lot of bug fixes:

https://people.debian.org/~mpitt/tmp/autopkgtest_3.6_3.9.3.debdiff

It's clearly wy outside the current freeze rules, but as it's not
an end user tool but rather an internal QA one, I want to at least
consider it. If we want to go that route, I'm happy to provide more
details.

1 2 >

1 - 100 of 190 matches

Mail list logo