package: src:rhsrvany
version: 1.1-2
severity: serious
tag: patch
runsrvany64 and runpnpwait64 autopkgtests can fail on amd64 on
ci.debian.net because of foreign arch wine32 installability issues
[0]. This currently prevents wine from migrating to testing [1].
The attached patch solves the
package: src:wine-development
severity: serious
This package is not intended to be released in a debian stable
release. This bug serves to prevent migration of the package to
testing.
Best wishes,
Mike
On Sat, Feb 13, 2021 at 5:01 AM Andreas Henriksson wrote:
> > For systems where awk is not yet installed (chroots), installation of
> > dash will currently fail since it's postinst calls add-shell from
> > debianutils.
>
> Please share details about how to reproduce this situation!
>
> You say you
package: src:debianutils
severity: serious
version: 4.11.2
tag: patch
debianutil's add-shell script uses awk, but awk is not an
Essential:yes package. For systems where awk is not yet installed
(chroots), installation of dash will currently fail since it's
postinst calls add-shell from
On Tue, Dec 22, 2020 at 3:45 AM Michel Le Bihan wrote:
> I my NMU 87.0.4280.88-0.2 has just been uploaded to unstable and I'm
> interested in joining and helping with the package. My work is in
> https://salsa.debian.org/mimi8/chromium/ . Please also see the
> discussion under
>
control: tag -1 moreinfo
control: severity -1 important
On Fri, Jun 19, 2020 at 11:09 PM Gong S. wrote:
> The current version of wine-development cannot launch any Windows programs,
> including built-in ones like "winecfg" and "wineconsole".
I am not able to reproduce this on i386. Is this on
On Fri, Apr 3, 2020 at 5:28 PM Stephen Kitt wrote:
> Thanks for the report, the package is missing a build-dependency on
> gcc-mingw-w64-x86-64.
There is more to it than this. I am working on it now.
> Michael, I can take care of fixing this, doing a rebuild to make sure and
> uploading, if you
package: src:glib2.0
severity: serious
version: 2.60.5-1
The latest glib2.0 upload fails to build on i386 and mips [0].
On i386, the gmenumodel test timed out. On mips, the gvariant test timed out.
Best wishes,
Mike
[0] https://buildd.debian.org/status/package.php?p=glib2.0
package: src:kopano-webapp
severity: serious
version: 3.5.6+dfsg1-1
kopano-webapp currently has a failing autopkgtest [0]. This currently
blocks migration of chromium since it is listed as an autopkgtest
dependency for this package.
control: tag -1 moreinfo
On Thu, Jun 13, 2019 at 5:36 AM Guillem Jover wrote:
> [23609:23609:0613/102304.872428:FATAL:render_process_host_impl.cc(4060)]
> Check failed: render_process_host->InSameStoragePartition(
> BrowserContext::GetStoragePartition(browser_context, site_instance, false )).
On Tue, Jun 11, 2019 at 2:21 PM Riku Voipio wrote:
> I can make an upload if you prefer, or I can wait for you.
No reason to delay, please go ahead.
Best wishes,
Mike
package: src:chromium
severity: serious
version: 75.0.3770.80-1
The latest upload fails to build on armhf due to missing intrinsics [0].
Best wishes,
Mike
[0]https://buildd.debian.org/status/fetch.php?pkg=chromium=armhf=75.0.3770.80-1=1560141959=0
package: src:chromium
severity: serious
version: 74.0.3729.108-1
The latest upload fails to build on arm64 due to errors in crc32 [0].
Best wishes,
Mike
[0]https://buildd.debian.org/status/fetch.php?pkg=chromium=arm64=74.0.3729.108-1=1556085401=0
control: tag -1 pending
On Tue, Feb 26, 2019 at 4:39 AM Lee Garrett wrote:
> your issue is related to mixing stable and testing, which is not supported and
> causing your issue here.
This may not be common knowledge, but mixed suites have always been a
supported configuration. This is a
control: tag -1 moreinfo
control: severity -1 minor
This sounds a lot like this upstream bug:
https://bugs.winehq.org/show_bug.cgi?id=23676
It is in a different app and only seen with mesa and ati drivers, not
nvidia. Which driver do you use?
Does AnyRail allow you to disable 3d rendering?
package: src:wine-development
severity: serious
version: 3.12-2
This has been fixed in wine [0]. It also needs to be fixed in wine-development.
Best wishes,
Mike
[0] http://bugs.debian.org/918666
On Mon, Dec 17, 2018 at 4:40 AM Bastian Blank wrote:
> > Since this can be used in place of chromium's setuid binary, my
> > opinion is that the Depends relationship on chromium-sandbox is no
> > longer required.
>
> Nope, at least if the package is supposed to work without admin
> intervention.
On Fri, Nov 16, 2018 at 4:30 AM Bastian Blank wrote:
> Debian does not support unprivileged user namespaces, so chromium needs
> to depend on -sandbox to get a working package.
The debian version of the kernel package provides
kernel.unprivileged_userns_clone as a runtime selectable option for a
control: tag -1 pending
On Tue, Aug 7, 2018 at 9:07 AM, Riku Voipio wrote:
> I didn't push this to main stretch branch, as the security upload commit
> is reconstructed rather the original from Michael. Changelog hasn't been
> updated either.
I had forgotten to push after the previous upload,
This will be fixed by the package now in unstable when it transitions
to testing in 5 days.
Best wishes,
Mike
control: tag -1 pending
On Fri, Jun 8, 2018 at 7:28 AM, Andreas Beckmann wrote:
> I don't think a -demos package should ship binaries with generic
> names in /usr/bin - and maybe not in /usr/bin at all.
I uploaded a new version fixing this last week, it is currently
awaiting review in NEW.
Best
package: src:gcc-6
version: 6.4.0-18
severity: grave
control: affects -1 src:chromium-browser
forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86166
This was marked as a duplicate upstream and closed, but it seems like
it should be considered a separate issue.
The latest chromium upload
On Sat, Jun 23, 2018 at 8:47 PM, 積丹尼 Dan Jacobson wrote:
> The browser won't let people switch back from 68 to 67 anyway,
> they would have to rip up their whole profile.
Have you ever considered not upgrading when packages land in
experimental? They are after all experimental.
Best wishes,
package: src:llvm-toolchain-6.0
version: 1:6.0-3
severity: serious
control: affects -1 src:chromium-browser
LLVM includes ConvertUTF, which has a non free license. See #823100,
#900596, etc. Files affected are:
lib/Support/ConvertUTF.cpp
include/llvm/Support/ConvertUTF.h
Best wishes,
Mike
package: src:chromium-browser
severity: grave
version: 68.0.3440.7-1
The version just uploaded to experimental causes an internal compiler
error in gcc on arm [0].
Best wishes,
Mike
[0]https://buildd.debian.org/status/package.php?p=chromium-browser=experimental
version: 67.0.3396.62-2
control: tag -1 confirmed, help
On Wed, Jun 6, 2018 at 11:37 AM, jim_p wrote:
> Is there any info on when this issue could be fixed? It has been a week since
> this bug report was opened and there are no official comments here regarding
> any progress, neither some newer source package suggesting
On Mon, Apr 23, 2018 at 4:57 PM, Markus Koschany wrote:
> lwjgl 2.9.3 is a legacy release from 2015. It is the last version of the
> 2.x series and no longer supported. Upstream moved to lwjgl 3. If nobody
> can fix this we should consider to remove lwjgl because the new version
> 3 would require
On Sun, Mar 4, 2018 at 3:44 PM, Salvatore Bonaccorso wrote:
> I've prepared an NMU for isc-dhcp (versioned as 4.3.5-3.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
Hi Salvatore,
Some meaningless whitespace is touched, but otherwise your patches
package: src:chromium-browser
version: 65.0.3325.73-1
severity: serious
Starting with chromium 65, arm64 fails while building skia.
../../third_party/skia/src/jumper/SkJumper_stages.cpp: In function 'F
from_half(U16)':
../../third_party/skia/src/jumper/SkJumper_stages.cpp:670:12: error:
Hi Salvatore,
The changes look correct to me. Please feel free to remove the delay
on the NMU.
Best wishes,
Mike
On Sat, Jul 22, 2017 at 3:57 AM, Salvatore Bonaccorso wrote:
> Control: tags 868952 + patch
> Control: tags 868952 + pending
>
> Dear maintainer,
>
> I've
control: severity -1 important
The impact of this is only reduced performance, which is not release
critical. This could be fixed by a stretch SPU later if someone is
interested in pushing that.
Best wishes,
Mike
On Mon, May 8, 2017 at 6:23 PM, Michael Gilbert wrote:
> I reviewed the diff. It does look correct to me, so please feel free
> to remove the delay.
There is also CVE-2017-3139 now [0].
Best wishes,
Mike
[0] https://access.redhat.com/errata/RHSA-2017:1202
On Sun, May 7, 2017 at 10:38 AM, Salvatore Bonaccorso wrote:
> I've prepared an NMU for bind9 (versioned as 1:9.10.3.dfsg.P4-12.3) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
Hi Salvatore,
I reviewed the diff. It does look correct to me, so please
control: severity -1 normal
control: retitle -1 lighttpd: suggest php-cgi since php5-cgi is removed
On Sun, Apr 9, 2017 at 6:56 AM, Carsten Schoenert wrote:
> the suggesting of the (currently wrong) package php5-cgi into a depends on
> package php7.0-cgi. Without this package lighttp isn't
control: severity -1 important
On Sun, Mar 12, 2017 at 1:26 AM, Andreas Beckmann wrote:
> /usr/lib/x86_64-linux-gnu/liblwres-export.so ->
> /lib/x86_64-linux-gnu/liblwres-export.so.141
> /usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.so.140.0.10
These are mistakenly included in
On Sun, Feb 5, 2017 at 6:47 AM, Bastian Blank wrote:
> bind9 uses /dev/random unconditionally without the possibility to change
> that in the configuration.
It is not entirely unconditional, --with-randomdev can be set at build
time, but admittedly that is not a very friendly solution.
Best
control: tag -1 -moreinfo
control: severity -1 normal
control: retitle -1 wpasupplicant: missing dependency on ifupdown on kfreebsd
On Mon, Feb 27, 2017 at 3:15 AM, Andrew Shadura wrote:
> Please provide more logs or debug info.
The error is limited to kfreebsd. Running with -dd produces a
package: wpasupplicant
severity: serious
justification: policy 3.5
version: 2.5-2+v2.4-3, 2:2.4-1
wpasupplicant relies on ifupdown, but there is no relationship to it
declared in the packaging.
For example, without ifupdown installed running these commands:
# ifconfig wlan0 create wlandev iwn0
control: tag -1 pending
Uploaded to delayed/5 to give -4 a chance to migrate.
Best wishes,
Mike
control: tag -1 moreinfo
On Fri, Feb 24, 2017 at 9:33 AM, Toni Mueller wrote:
> Package: xserver-xorg-core
Did you only install xserver-xorg-core? If so, you will be missing a
lot of important packages, like xserver-xorg-input-libinput, which
provides mouse support. To get all packages needed,
control: tag -1 moreinfo
I tried rar on up to date i386 and amd64 stretch systems. Versions
5.3 and 5.4 both work fine for me.
I am not sure if this is related or not, but linux 4.8.15-1 changes
vsyscall, which was mentioned in message #25.
Has anyone else tested this lately?
Best wishes,
package: src:bind9
severity: grave
version: 1:9.10.3.dfsg.P4-11
The fix for this issue causes more regressions.
package: chromium-widevine
severity: serious
version: 55.0.2883.75-6
Just like #824169, the contrib dbgsym binary package causes the source
package to be duplicated in contrib.
Best wishes,
Mike
On Wed, Feb 1, 2017 at 2:19 PM, Riku Voipio wrote:
> Can you push the current experimental to git so I can merge the
> fix on top of it, or should I just do it myself?
Just pushed now, I had it all staged a while back but forgot to push.
Apologies.
Best wishes,
Mike
package: src:chromium-browser
severity: grave
version: 56.0.2924.76-1
The upload to experimental fails to build on armhf due to new NEON code.
Best wishes,
Mike
On Thu, Jan 26, 2017 at 6:41 AM, Arturo Borrero Gonzalez wrote:
> could you please share yours plans regarding this bug?
Patches welcome?
Best wishes,
Mike
On Sun, Jan 22, 2017 at 6:26 AM, Luca Boccassi wrote:
> This will allow a clean rebuild for backporting purposes. Would really
> appreciate a lot if this change could be made :-)
There are no jessie backports of bind.
Best wishes,
Mike
control: severity -1 wishlist
control: retitle -1 chromium: add extensions option to CHROMIUM_FLAGS
This update does not remove anything, so there is no reason to think
there is data loss.
I agree that setting the option in CHROMIUM_FLAGS should be supported.
Best wishes,
Mike
On Fri, Jan 13, 2017 at 4
> Upstream has actually added a patch for this already in the stable
> branch as far as I know, so I expect this to actually have been
> fixed in 9.10.4-P5.
I worked on this today, their patch is not applied in -P5, so I'll be
uploading a version with Bernhard's
On Sun, Nov 20, 2016 at 9:16 PM, Jens Reyer wrote:
> wine-development 1.9.22-1 (in stretch) built successfully on all
> architectures when it was uploaded to unstable, but fails to
> build in a stretch environment on i386 now (amd64 is still fine).
> Exactly the same for 1.9.23-1 on i386 in a sid
control: severity -1 important
control: forwarded -1 http://crbug.com/571277
There are a few suggestions in the upstream bug, do any of them help?
Also bug #833342 seems similar.
Best wishes,
Mike
control: severity -1 important
control: tag -1 moreinfo, unreproducible
On Mon, Feb 29, 2016 at 4:11 PM, Joerg Frings-Fuerst wrote:
> $ systemctl start isc-dhcp-server
> Failed to start isc-dhcp-server.service: The name org.freedesktop.PolicyKit1
> was not provided by any .service files
The
contlol: severity -1 normal
On Sun, Apr 3, 2016 at 3:43 AM, LACROIX Jean Marc wrote:
> On recent Debian Kernel (3.16.7-ckt25-1) based on Jessie 8.4, i try to
> setup one bridge (br-admin) with 2 externals devices.
The description that follows isn't totally clear, are you saying that
this worked
On Wed, Mar 9, 2016 at 10:20 AM, Markus Koschany wrote:
> https://github.com/JetBrains/kotlin
>
> This one seems to be the blocker because kotlin build-depends on
> components of IntelliJ IDEA and all in all that's a lot of stuff for a
> mere library.
This is the huge dependency stack that I was
> I have switched the build-dependency to default-jdk and changed
> JAVA_HOME in debian/rules accordingly. However the package FTBFS with
> OpenJDK 8. I guess packaging the latest upstream release would be the
> best option.
2.9.3 is supposed to support building without ant. I looked at it a
package: src:chromium-browser
severity: grave
version: 46.0.2490.71-1
The latest upstream versions exhaust memory with ld.bfd as the linker
on i386. The gold linker so far seems to avoid this.
On Wed, Dec 16, 2015 at 3:22 PM, Raphael Hertzog wrote:
> Hello dear maintainer(s),
>
> the Debian LTS team would like to fix the security issues which are
> currently open in the Squeeze version of bind9:
> https://security-tracker.debian.org/tracker/CVE-2015-8000
As mentioned before, please go
On Wed, Dec 16, 2015 at 10:11 AM, Salvatore Bonaccorso wrote:
> Hi,
>
> Attached is proposed debdiff for the unstable upload (not yet uploaded
> to any delayed queue, just want to check I do not interfere with your
> work on it already).
You can do the nmu. I don't have time right now.
Best
On Wed, Aug 26, 2015 at 7:11 PM, Linus Torvalds wrote:
So quite frankly, the fact that Debian people now attack Dirk, who has
been bending over backwards over these kinds of stupidities, is not a
big surprise. I think it's in the Debian DNA to care more about rules
than about technical sanity.
control: reassign -1 src:fglrx-driver
On Sat, Aug 15, 2015 at 4:23 AM, Richard Jasmin wrote:
It seems either development is stalled on open source drivers or we have an
upstream issue in the video department.
[...]
Versions of packages xserver-xorg depends on:
ii fglrx-driver
control: reassign -1 src:fglrx-driver
On Sat, Aug 15, 2015 at 4:23 AM, Richard Jasmin wrote:
It seems either development is stalled on open source drivers or we have an
upstream issue in the video department.
[...]
Versions of packages xserver-xorg depends on:
ii fglrx-driver
control: tag -1 moreinfo, unreproducible, -security
control: severity -1 important
On Fri, Aug 7, 2015 at 7:08 PM, reinhard wrote:
Package: bind9-host
Version: 1:9.8.4.dfsg.P1-6+nmu2+deb7u4
Severity: serious
File: bind9
Tags: security
Justification: fails to build from source (but built
Source: mrpt
Version: 1:1.2.2-1.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11
This package fails to build with the new libstdc++ ABI (with updated
libassimp3, #794835).
The error has
05:12:07.0 +
@@ -1,3 +1,11 @@
+assimp (3.0~dfsg-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Build with g++ 5 and update symbols for the libstdc++ ABI change
+(closes: #794835).
+
+ -- Michael Gilbert mgilb...@debian.org Sat, 08 Aug 2015 20:57:10 +
+
assimp
On Wed, Jul 29, 2015 at 2:15 AM, Salvatore Bonaccorso wrote:
Control: tags 793903 + pending
Hi Mike,
I've prepared an NMU for bind9 (versioned as 1:9.9.5.dfsg-10.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I should
delay it longer or if I should cancel it instead and you
at 00:49 -0400, Michael Gilbert wrote:
Barring the obtusely incorrect rootkit miscategorization
Well, as I've said,.. no one can really tell what it is, since it's a
blob,... and even if one would assume that someone could correctly
reverse engineer it, or reproducibly build it from public sources
On Thu, Jun 18, 2015 at 8:23 PM, Christoph Anton Mitterer wrote:
- still no DSA (or something like that)
See previous message.
- still no concentrated effort at the Debian level to pro-actively work
against such sources that include or more or less secretly download
blobs
If you have an
On Thu, Jun 18, 2015 at 7:33 PM, Steven Chamberlain wrote:
Steven Chamberlain wrote:
would the
DFSG chromium browser be 'more' free if it disabled NaCl?
Actually, in the build log I see disable_nacl=1
I'm confused that hotword-x86-64.nexe is a NaCl module [0], even
though Debian's chromium
On Mon, Jun 15, 2015 at 11:16 PM, Christoph Anton Mitterer wrote:
Shouldn't we see a DSA following this incident?
Since no one really know which binaries have been downloaded there and
what they actually do, and since it cannot be excluded that it was
actually executed, such systems are
control: tag -1 confirmed, help
On Wed, May 27, 2015 at 7:25 AM, Yves-Alexis Perez wrote:
Note that the binary blob is executed throught native client, which is
not enabled by default, so I /think/ you need explicit action from the
user (although if you enable NaCl for something else, then you
On Mon, May 25, 2015 at 6:16 AM, Adam Borowski wrote:
When trying to start doomsday, it pops up a dialog which says:
.[ Doomsday Engine ]
App init failed:
[NotFoundError] (Record::subrecord) Subrecord 'alert' not found
`
then crashes with a segmentation fault.
This seems to be
On Sun, May 17, 2015 at 5:14 PM, Javier Barroso wrote:
Hello,
After apt update; apt dist-upgrade ; doesn't advance because this bug,
I tried to use apt-get to remove broken packages, but I was not able
to know how apt-get could solve this issue (holding/purging or
rollbacking *wine*
control: tag -1 confirmed
control: retitle -1 gparted: fails to start with gvfs installed
I missed this during testing since I don't use gvfs. gparted can be
made to work again if the gvfs package is removed, but that of course
is not a real solution.
Best wishes,
Mike
--
To UNSUBSCRIBE,
On Sat, Apr 18, 2015 at 4:49 PM, Søren Holm wrote:
Removing gvfs does not work.
You'll probably need to reboot to get gvfs to completely go away. See:
https://bugs.debian.org/544148
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
On Sat, Apr 18, 2015 at 6:31 PM, Søren Holm wrote:
I did - didn't work :(
I guess there is more to it then, at least on lxde removing gvfs is
all it takes. For other DEs you'll need to do some work to figure out
which other piece is also a problem.
Best wishes,
Mike
--
To UNSUBSCRIBE, email
control: reassign -1 udisks2
control: affects -1 gparted
control: retitle -1 udisks2-inhibit mount move fails
The problem is actually udisks2-inhibit. The upstream fix for #781716
relies on that, but it doesn't seem to work:
$ sudo /usr/lib/udisks2/udisks2-inhibit /usr/bin/true
mount: bad
control: severity -1 normal
On Wed, Apr 15, 2015 at 3:16 AM, Andrey Rahmatullin wrote:
Reading symbols from kvpnc...Reading symbols from
/usr/lib/debug//usr/bin/kvpnc...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Debugging symbols is a should in debian policy.
control: severity -1 wishlist
control: forwarded -1 https://freedesktop.org/patch/34445
control: retitle -1 mesa: use llvm's getCPUTargetFeatures() instead of
getHostCPUName()
It turns out that mesa uses llvm's getHostCPUName(), and qemu i386 by
default (correctly) reports itself as pentium2,
+++ motif-2.3.4/debian/changelog 2015-04-15 20:31:50.0 -0400
@@ -1,3 +1,10 @@
+motif (2.3.4-6.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove symbol that was intended to be private.
+
+ -- Michael Gilbert mgilb...@debian.org Thu, 16 Apr 2015 00:16:42 +
+
motif (2.3.4-6.1
On Wed, Apr 15, 2015 at 3:12 PM, Paul Gevers wrote:
Hi all,
All the builds of motif failed [1] due to a missing symbol. What are we
going to do? I saw that Graham already choose to just remove the symbol
from the Ubuntu package. I believe that this is really a no-no,
especially without
control: tag -1 unreproducible, moreinfo
On Wed, Apr 15, 2015 at 1:29 PM, Mario Lang wrote:
openmpi fails to build:
$ apt-get source openmpi
$ cd openmpi-1.6.5
$ dpkg-buildpackage -uc -us
(log attached)
Note that the problem seems to be related to timestamping of
config/libtool.m4 (at
control: severity -1 important
Given the straightforward workaround, this isn't a grave issue.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
+using udisks2 (closes: #781716).
+
+ -- Michael Gilbert mgilb...@debian.org Sun, 12 Apr 2015 18:31:55 +
+
gparted (0.19.0-2) unstable; urgency=medium
* 03_fix-crash.patch: cherry pick of upstream commit that fixes
diff -Nru gparted-0.19.0/debian/patches/04_inhibit-udisks2.patch gparted
:03.0 +
@@ -1,3 +1,10 @@
+motif (2.3.4-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Disable buggy fix for upstream bug #1565 (closes: #781995).
+
+ -- Michael Gilbert mgilb...@debian.org Sun, 12 Apr 2015 19:25:51 +
+
motif (2.3.4-6) unstable; urgency=medium
On Sun, Apr 12, 2015 at 5:14 PM, Graham Inggs wrote:
So what is the best way forward?
I have no problems with Michael's upload (thanks!) apart from the delay.
I can reschedule to delayed/0 if as the maintainer you say that's ok.
Paul and I were just considering adding the line:
Recommends:
control: severity -1 normal
On Fri, Apr 10, 2015 at 8:13 PM, Christoph Anton Mitterer wrote:
ii libdvdcss2 [libdvdcss] 1.3.0-dmo1
Your system is tainted by deb-multimedia.org.
Kernel: Linux 3.19.0-trunk-amd64 (SMP w/8 CPU cores)
Also possibly kernel related. Please try the jessie kernel.
control: severity -1 important
control: retitle -1 libmono-corlib4.5-cil: possible dpkg trigger cycle
On Wed, Mar 25, 2015 at 5:26 PM, Niels Thykier wrote:
Is this upgrade problem still reproducible? There was an upload of dpkg
between you filing this upload. I do realise this does not affect
control: severity -1 important
On Mon, Mar 9, 2015 at 10:07 AM, Gianluca Oglietti wrote:
If the problem is the kernel, can you suggest me a way to debug this issue?
Try starting a discussion on the linux kernel mailing list (lkml.org)
or bugzilla (bugzilla.kernel.org).
Best wishes,
Mike
--
control: severity -1 important
On Wed, Mar 25, 2015 at 1:21 PM, Dominik George wrote:
This bug is possibly security relevant because the intention of the
script, namely separating user directories in /dev/shm, is entirely
defeated. As a matter of lucky fact, / is not writable by regular users.
control: severity -1 important
This looks like it no longer needs to be release critical since
#731341 was fixed without changes to kbuild.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
package: src:icu
version: 52.1-7.1
severity: serious
tags: security
Google added another check in a later patch for this issue, which
wasn't included in the previous nmu:
https://chromium.googlesource.com/chromium/deps/icu/+/a626a75aad2675254073366fcaa9465dacf17100/patches/col.patch
Best wishes,
control: tag -1 patch, pending
On Sat, Mar 14, 2015 at 9:48 PM, Michael Gilbert wrote:
Google added another check in a later patch for this issue, which
wasn't included in the previous nmu:
Hi,
I uploaded an nmu to delayed/3 fixing this problem. Please see attached.
Best wishes,
Mike
diff
On Sun, Feb 22, 2015 at 6:35 AM, Christian Kastner wrote:
In wheezy and later, where /etc/sudoers already is a conffile, that is
entirely for dpkg to handle, not for the *.preinst scripts. Anything in
the *.preinst is exclusively for when upgrading from squeeze.
So, the more I think about it,
On Fri, Feb 20, 2015 at 10:49 AM, Salvatore Bonaccorso wrote:
Control: tags 22 + pending
Dear maintainer,
I've prepared an NMU for xdg-utils (versioned as 1.1.0~rc1+git20111210-7.4)
and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Hi Salvatore,
control: forcemerge 775235 -1
On Fri, Feb 6, 2015 at 1:20 PM, Simon McVittie wrote:
Michael, I see you've found a solution or workaround: is there
anything you'd like Rafal to try?
Try gnome-shell built with llvm-3.4 instead of 3.5.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to
control: severity -1 important
Without any feedback or debugging, and since you're the only one
experiencing these problems, there isn't much that can be done.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
removed (closes: #776137).
+
+ -- Michael Gilbert mgilb...@debian.org Sun, 22 Feb 2015 00:30:33 +
+
sudo (1.8.11p2-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru sudo-1.8.11p2/debian/sudoers sudo-1.8.11p2/debian/sudoers
--- sudo-1.8.11p2/debian/sudoers 2014-10-30 18:24
On Sat, Feb 21, 2015 at 9:52 PM, Christian Kastner wrote:
It's not backed up in jessie or later. The backup/md5sum stuff is
preceeded by a test for and old version less than 1.7.4p4-4, so in
wheezy and later, all the md5sum stuff is ignored during upgrades.
It is most certainly backed up in
package: src:bind9
severity: serious
tags: security
A new security issue was disclosed for bind9:
https://security-tracker.debian.org/tracker/CVE-2015-1349
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
1 - 100 of 1088 matches
Mail list logo