Bug#988473: unblock: gnome-sound-recorder/3.38.1-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package gnome-sound-recorder
[ Reason ]
The new upstream release fixes an UI bug which people argue is RC,
see #988292
(This also means dropping a commit previously carried in debian/patches/
as it's now part of the release.)
[ Impact ]
Using spacebar doesn't work properly in UI ("causes data loss").
[ Tests ]
I've run the program. No other testing. Both the old and new
version works fine for my personal use.
[ Risks ]
The practical change here is adding 2 lines of code setting two
properties in src/recorderWidget.js, dropping unusable m4a format
support (which likely noone uses since we never got a bug report),
updates translations. Should be very low risk.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
The new upstream release also includes translation updates and some
metadata to go with the release. Attached diff has been slighly
filtered so you don't have to scroll through the translations.
Please note that the debian/patches and src/row.js changes cancel
each other out. (Dropped patch now part of new upstream release.)
unblock gnome-sound-recorder/3.38.1-1
$ git diff debian/3.38.0-3..debian/3.38.1-1 | filterdiff -x '*/po/*'
diff --git a/NEWS b/NEWS
index bd9e05a..9d5d540 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,12 @@
+ 3.38.1
+ ==
+ Translation updates
+ Fix export dialog for recordings disappears shortly after opening
+ Fix not able to use space bar in recording name input
+ Fix recording is lost when using space bar in name input
+ Fix ui becomes unusable and recording is lost after stopping a record
+ Remove m4a option since using it results in unusable recordings
+
3.34.0
==
Translation updates
diff --git a/data/appdata/org.gnome.SoundRecorder.metainfo.xml.in.in b/data/appdata/org.gnome.SoundRecorder.metainfo.xml.in.in
index 4b1db05..a9bd409 100644
--- a/data/appdata/org.gnome.SoundRecorder.metainfo.xml.in.in
+++ b/data/appdata/org.gnome.SoundRecorder.metainfo.xml.in.in
@@ -35,6 +35,31 @@
+
+
+Bugfix release
+
+
+Translation updates
+
+
+Fix export dialog for recordings disappears shortly after opening
+
+
+Fix not able to use space bar in recording name input
+
+
+Fix recording is lost when using space bar in name input
+
+
+Fix ui becomes unusable and recording is lost after stopping a record
+
+
+Remove m4a option since using it results in unusable recordings
+
+
+
+
An overall update of Sound Recorder's design
@@ -69,4 +94,8 @@
The GNOME Project
meg387_at_gmail.com
@gettext-package@
+
+workstation
+mobile
+
diff --git a/data/org.gnome.SoundRecorder.desktop.in.in b/data/org.gnome.SoundRecorder.desktop.in.in
index 0bb63f3..8cf7c4d 100644
--- a/data/org.gnome.SoundRecorder.desktop.in.in
+++ b/data/org.gnome.SoundRecorder.desktop.in.in
@@ -9,4 +9,6 @@ Categories=GNOME;GTK;Audio;AudioVideo;
Keywords=Audio;Application;Record;
Exec=gnome-sound-recorder
StartupNotify=true
+# Translators: Do NOT translate or transliterate this text (these are enum types)!
+X-Purism-FormFactor=Workstation;Mobile;
diff --git a/data/org.gnome.SoundRecorder.gschema.xml.in b/data/org.gnome.SoundRecorder.gschema.xml.in
index 4cf6c09..afe84b2 100644
--- a/data/org.gnome.SoundRecorder.gschema.xml.in
+++ b/data/org.gnome.SoundRecorder.gschema.xml.in
@@ -4,7 +4,6 @@
-
diff --git a/data/ui/window.ui b/data/ui/window.ui
index e29196e..53bcdef 100644
--- a/data/ui/window.ui
+++ b/data/ui/window.ui
@@ -308,11 +308,6 @@
app.audio-profile
mp3
-
-M4A
-app.audio-profile
-m4a
-
Audio Channel
diff --git a/debian/changelog b/debian/changelog
index 57dffcf..0b1103a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+gnome-sound-recorder (3.38.1-1) unstable; urgency=medium
+
+ * Team upload.
+ * New upstream release (Closes: #982874, #988292)
+ * Revert "Add patch to fix "export" dialog disappearing due to GC"
+- now part of new upstream release.
+
+ -- Andreas Henriksson Thu, 13 May 2021 18:19:57 +0200
+
gnome-sound-recorder (3.38.0-3) unstable; urgency=medium
* Team upload
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 4ed071a..e447a39 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,7 +1,7 @@
[DEFAULT]
pristine-tar = True
-debian-branch = debian/master
-upstream-branch = upstream/latest
+debian-branch = debian/bullseye
+upstream-branch =
Bug#1034016: unblock (pre-approval): debos/1.1.1-2.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: de...@packages.debian.org
Control: affects -1 + src:debos
Hello release-team,
I'm looking for a pre-approval for an unblock of my NMU of debos,
which contains 3 commits cherry-picked from upstream.
The main bug to fix is https://bugs.debian.org/1027787
The current version of debos in bookworm is not compatible with
bookworm. The maintainer promised me to deal with this if I
submitted an upstream PR where he merged my patch for it,
but apparently never found the time to update the debian
package.
While at it I also cherry-picked 2 documentation fixes.
I'm attaching a debdiff, but if you'd like to avoid reading
patch-in-patch these are the commits:
https://github.com/go-debos/debos/commit/18998ffaf78321e111d9823b3180eca3fa4593f6
https://github.com/go-debos/debos/commit/f4ff78305513a90eca089e33f7bba35bffa96bd1
https://github.com/go-debos/debos/commit/c8c5075853aab9e1ac6ae07a3a7c2b070aa38a62
unblock debos/1.1.1-2.1
diff -Nru debos-1.1.1/debian/changelog debos-1.1.1/debian/changelog
--- debos-1.1.1/debian/changelog2022-10-31 11:16:08.0 +0100
+++ debos-1.1.1/debian/changelog2023-03-16 10:09:37.0 +0100
@@ -1,3 +1,13 @@
+debos (1.1.1-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Cherry-pick upstream commit that unbreaks bookworm (Closes: #1027787)
+ * Cherry-pick upstream doc fix for non-free-firmware
+ * Cherry-pick upstream example fix for interactive password prompt
+(Closes: #1006823)
+
+ -- Andreas Henriksson Thu, 16 Mar 2023 10:09:37 +0100
+
debos (1.1.1-2) unstable; urgency=medium
* Run autopkgtest in an isolated virtual machine
diff -Nru debos-1.1.1/debian/patches/0001-Limit-old-suite-workaround.patch
debos-1.1.1/debian/patches/0001-Limit-old-suite-workaround.patch
--- debos-1.1.1/debian/patches/0001-Limit-old-suite-workaround.patch
1970-01-01 01:00:00.0 +0100
+++ debos-1.1.1/debian/patches/0001-Limit-old-suite-workaround.patch
2023-03-16 10:09:37.0 +0100
@@ -0,0 +1,65 @@
+From: Andreas Henriksson
+Date: Tue, 3 Jan 2023 01:12:42 +0100
+Subject: Limit old suite workaround
+
+The workaround for https://github.com/go-debos/debos/issues/361
+that was applied in
https://github.com/go-debos/debos/commit/b3c1f76bcc1dbd55fef584b8ddbda33f12733116
+breaks recipes for bookworm and newer.
+
+Signed-off-by: Andreas Henriksson
+(cherry picked from commit 18998ffaf78321e111d9823b3180eca3fa4593f6)
+---
+ actions/debootstrap_action.go | 26 +-
+ 1 file changed, 25 insertions(+), 1 deletion(-)
+
+diff --git a/actions/debootstrap_action.go b/actions/debootstrap_action.go
+index e354ff4..e7c2587 100644
+--- a/actions/debootstrap_action.go
b/actions/debootstrap_action.go
+@@ -53,6 +53,7 @@ package actions
+ import (
+ "fmt"
+ "io"
++ "log"
+ "os"
+ "path"
+ "strings"
+@@ -158,6 +159,24 @@ func (d *DebootstrapAction) RunSecondStage(context
debos.DebosContext) error {
+ return err
+ }
+
++// Guess if suite is something before usr-is-merged was introduced
++func (d *DebootstrapAction) isLikelyOldSuite() bool {
++ switch strings.ToLower(d.Suite) {
++ case "sid", "unstable":
++ return false
++ case "testing":
++ return false
++ case "bookworm":
++ return false
++ case "trixie":
++ return false
++ case "forky":
++ return false
++ default:
++ return true
++ }
++}
++
+ func (d *DebootstrapAction) Run(context *debos.DebosContext) error {
+ d.LogStart()
+ cmdline := []string{"debootstrap"}
+@@ -204,7 +223,12 @@ func (d *DebootstrapAction) Run(context
*debos.DebosContext) error {
+ cmdline = append(cmdline, fmt.Sprintf("--variant=%s",
d.Variant))
+ }
+
+- cmdline = append(cmdline, "--exclude=usr-is-merged")
++ // workaround for https://github.com/go-debos/debos/issues/361
++ if d.isLikelyOldSuite() {
++ log.Println("excluding usr-is-merged as package is not in
suite")
++ cmdline = append(cmdline, "--exclude=usr-is-merged")
++ }
++
+ cmdline = append(cmdline, d.Suite)
+ cmdline = append(cmdline, context.Rootdir)
+ cmdline = append(cmdline, d.Mirror)
diff -Nru
debos-1.1.1/debian/patches/0002-Include-non-free-firmware-component-in-Simple-exampl.patch
debos-1.1.1/debian/patches/0002-Include-non-free-firmware-component-in-Simple-exampl.patch
---
debos-1.1.1/debian/patches/0002-Include-non-free-firmware-component-in-Simple-exampl.patch
1970-01-01 01:00:00.0 +0100
+++
debos-1.1.1/debian/patches/0002-Include-non-free-firmware-component-in-Si
Re: Bug#1034016: unblock (pre-approval): debos/1.1.1-2.1
Hello Chris, On Thu, Apr 06, 2023 at 04:37:30PM +0100, Christopher Obbard wrote: > Hi Andreas, > > As the upstream maintainer, I can just tag a new version upstream as 1.1.2 & > pick that in Debian. > Then I hope it can flow into bookworm? I wonder if the release team will accept a new upstream release at this point in the freeze We're pretty deep into the hard freeze at this point (but I don't have enough insight into how the release team works these days, it seems much more relaxed than in the old times where I was more involved and basically any extra character would get you a NACK, specially an "unneccessary" upstream version number change). Do you have time to do all the work and still accept a potential NO from the release team? Please be honest to yourself. IMHO it feels much safer to just go with a targeted upload (which is now also already approved), but if you feel strongly about it and also think you have time to pursue a new release then just send me a NACK on the NMU (ASAP! I'm ready to upload *now*) and I will not pursue it. > > The past few months have been... quite crazy in my personal life so I > haven't gotten around to doing this as yet. Huge apologies for that, > it is on my radar this week. > > Hope that is acceptable to you? No need to apologize. We're all busy sometimes and that's why we have NMUs so we can help each other out. (I've also been quite busy or the NMU would have happened much sooner in the release cycle.) Thanks for all the work you have had time to do! > > Thanks, > > Chris Regards, Andreas Henriksson PS. Feel free to ignore my NMU and just upload the new upstream release once we're past the freeze/release and the development opens up again.
Re: Bug#1034016: unblock (pre-approval): debos/1.1.1-2.1
Hello, On Thu, Apr 06, 2023 at 05:52:32PM +0100, Christopher Obbard wrote: > Hi Andreas, > > On Thu, 2023-04-06 at 18:45 +0200, Andreas Henriksson wrote: [...] > > IMHO it feels much safer to just go with a targeted upload [...] > > Let's go with your NMU, since you've done all of the work already, then I > will upload the new version into unstable once development opens. > > How does that sound? > > PS: Can you push your source to salsa? Pushed to salsa (incl. tag)! dput new version, so should hopefully he accepted for unstable soon! Thanks for the quick followup! Regards, Andreas Henriksson
Bug#1022003: transition: gssdp/gupnp 1.2->1.6 (+ rygel 0.42.0)
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello release team,
I'd like to transition gssdp/gupnp to 1.6 version as part of current
GNOME release.
I've just uploaded the new versions of gssdp and gupnp 1.6.0 to
binary-NEW/experimental.
I will team-upload new releases of the following reverse dependencies as
part of gnome-team:
* rygel (0.42.0-1 just uploaded to binary-NEW/experimental)
- FYI internal soname bump for broken plugin ABI, but there are no
external plugins (all built from src:rygel).
* gupnp-tools (0.12.0-1 just uploaded to experimental)
* gupnp-igd (needs cherry-pick
https://gitlab.gnome.org/GNOME/gupnp-igd/-/commit/79a1e4cf8c256132978a1d8ab718c8ad132386de
)
I've just done QA uploads to unstable for latest version of
dleyna-{core,renderer,server} to make it easier to cherry-pick upstream
changes for gssdp/gupnp 1.6 (not yet in a released version).
I can do qa uploads of dleyna-* but would prefer if these packages where
simply removed from testing as they've been orphaned for many years
(since their initial upload to debian).
Will file a bug for each package and point out the upstream commits
respectively:
*
https://github.com/phako/dleyna-core/commit/b88f231affc697be813d7c77c17e3130df81cb9a
*
https://github.com/phako/dleyna-renderer/commit/b3a06c8bc4b91803d7bde312f49a68109b8ad8d4
*
https://github.com/phako/dleyna-server/commit/e7f64192643f5783e19482a11697de9ec3eea033
I will file bugs for remaining (and offer to NMU if no response),
fixed-upstream (not yet in a released version):
* caja-extensions -- https://github.com/mate-desktop/caja-extensions/issues/110
* librm --
https://gitlab.com/tabos/librm/-/commit/c9aae663ff40c1ab171476652eba68c174d96ba2
+
https://gitlab.com/tabos/librm/-/commit/a849d9a6a6624d5f3c6a70dd63590d1a2b79d1af
Regards,
Andreas Henriksson
PS. Once I've filed all bug reports I'll set them as blockers for this bug
report.
Ben file:
title = "gupnp";
is_affected = .depends ~ "libgupnp-1.2-1" | .depends ~ "libgssdp-1.2-0" |
.depends ~ "libgupnp-1.6-0" | .depends ~ "libgssdp-1.6-0";
is_good = .depends ~ "libgupnp-1.6-0" | .depends ~ "libgssdp-1.6-0";
is_bad = .depends ~ "libgupnp-1.2-1" | .depends ~ "libgssdp-1.2-0";
Bug#1022003: transition: gssdp/gupnp 1.2->1.6 (+ rygel 0.42.0)
Control: tags -1 - moreinfo On Tue, Oct 18, 2022 at 09:32:10PM +0200, Sebastian Ramacher wrote: > Control: tags -1 moreinfo [...] > Please remove the moreinfo tag once they cleared NEW. [...] All of them (gssdp, gupnp and rygel) has made it through NEW, thus removing moreinfo tag. I'll start working on local updates and build-testing reverse dependencies next to verify the transition really is as easy as anticipated. Regards, Andreas Henriksson
Bug#1022003: transition: gssdp/gupnp 1.2->1.6 (+ rygel 0.42.0)
Hello,
I've just started looking at building patched reverse dependencies and
ran into some issues.
librm has upstream commits that adds support for gssdp/gupnp 1.6, but
apparently hasn't actually ported to libsoup-3.0 yet so it completely
fails to build if using this... upstream issue filed and followed up on
the librm blocker bug.
This is probably the main blocker for this transition to proceed now,
unless you're willing to temporarily remove src:librm and its reverse
dependency roger-router from testing.
caja-extensions doesn't seem to use soup API's directly, but I can't
test-build since building is currently blocked by the ongoing perl
transition.
dleyna-{core,renderer,server} is now upstream maintained by the same
person maintaining gssdp/gupnp/rygel, so I presume this port actually
works but as mentioned I'd prefer to RM these rather than keep
carrying the orphanage.
Regards,
Andreas Henriksson
Bug#1022003: transition: gssdp/gupnp 1.2->1.6 (+ rygel 0.42.0)
On Wed, Oct 19, 2022 at 09:17:41PM +0200, Sebastian Ramacher wrote: > Control: block -1 by 1019353 [...] > Let's see where we are after the perl transition. Depending on how > responsive librm upstream is, that might give them enough time to fix > the remaining issues. [...] ACK, but I'd also like to say that's probably not very likely to happen. The support for gssdp/gupnp 1.6 was merged to librm upstream master 10 months ago. They've apparently never even tried to compile-test it before or after this merge. Relevant popcon link says basically noone even uses it: https://qa.debian.org/popcon-graph.php?packages=librm0%2Croger-router&show_installed=on&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 While I have no personal interest in roger-router/librm beyond this transition, I've quickly looked at what's involved in porting librm to libsoup-3.0 and it's more changes needed then I'm comforable doing without having any way to test the result. (I probably could also not keep my hands away from fixing memory leaks, off-by-one errors, and other quality issues in the code that I immediately noticed while poking at it which would further extend how much work it would need.) I guess we'll just have to wait and hope (I could probably ask gupnp upstream about help since he's usually very helpful, but I'm not sure it's a useful activity for him to spend time on.) Regards, Andreas Henriksson
Bug#1022003: transition: gssdp/gupnp 1.2->1.6 (+ rygel 0.42.0)
Hello Sebastian Ramacher, On Thu, Oct 27, 2022 at 07:38:14PM +0200, Sebastian Ramacher wrote: > Control: tags -1 = confirmed > > On 2022-10-18 21:24:03 +0200, Andreas Henriksson wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > > > Hello release team, > > > > I'd like to transition gssdp/gupnp to 1.6 version as part of current > > GNOME release. > > Please go ahead I'll hold off a few more days if that's not a problem. Both because I'll be a bit busy the next couple of days but also because there was a (newly added) test that failed on s390x in gupnp/experimental. With help from upstream the actual bug in gssdp/experimental should be fixed, new gssdp/experimental has built (except on ppc64el) and I've done a giveback of gupnp/experimental on s390x but it has still not built yet confirming if the problem is actually fixed and the test passes. Is there any chance you have a way to give some priority to gupnp/experimental on s390x? https://buildd.debian.org/status/package.php?p=gupnp&suite=experimental I'll probably also look into doing some NMUs to experimental of rdeps before kicking off the actual transition. If this means you want to put me back on hold and give the slot to someone else, that's fine with me! I just want to make sure we get this transition done before freeze so gnome versions are all synced up. Regards, Andreas Henriksson PS. Thanks for being very responsive through this process. A few years ago waiting several months without hearing anything was common and kind of what I still was expecting. This feels alot more like coordinating in the real sense of the word.
Bug#1022003: transition: gssdp/gupnp 1.6: Status update + prepared to start
TL;DR I consider myself ready to start the transition now, with removals in the plan. * gupnp/experimental has now successfully built on s390x - this verifies gssdp 1.6.0-2 (with patch from upstream) fixes an old bug caught by the (new) gupnp test * Note: ppc64el has still not built experimental packages yet * Following rdeps are now prepared in experimental: - rygel 0.42.0-1 - gupnp-tools 1.2.0-1 - gupnp-igd 1.2.0-2 - caja-extensions 1.26.1-1.1 * Plan to file for RM RoQA dleyna - has a new upstream and 4 repos/sources merged into 1. - NEW dleyna 0.8 packages prepped in https://salsa.debian.org/debian/dleyna - needs maintainer + NEW - details in https://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/2022-October/174113.html ( #1022009 #1022010 #1022011 #1023093 ) - I will possibly upload 0.8 to experimental for exposure after transition is done (via NEW, not sure if Debian QA maintained packages is accepted in NEW). * Suggestion to temporarily remove librm (+ roger-router) from testing - as previously mentioned upstream porting to gssdp/gupnp 1.6 is broken - needs porting to libsoup 3.0 - upstream main branch has had this issue for 10+ months. - No response yet in https://gitlab.com/tabos/librm/-/issues/4 or #1022008 Unless someone tells me I missed something I'll start uploading to unstable as soon as I feel I have a free time slot (which might be later today). Regards, Andreas Henriksson
Bug#1022003: transition: gssdp/gupnp 1.6: Status update + prepared to start
Hello, On Sun, Oct 30, 2022 at 09:46:11AM +0100, Andreas Henriksson wrote: > TL;DR I consider myself ready to start the transition now, with removals > in the plan. [...] > Unless someone tells me I missed something I'll start uploading to > unstable as soon as I feel I have a free time slot (which might be later > today). gssdp_1.6.0-3_source.changes ACCEPTED into unstable gupnp_1.6.0-3_source.changes ACCEPTED into unstable gupnp-igd_1.2.0-3_source.changes ACCEPTED into unstable gupnp-tools_0.12.0-2_source.changes ACCEPTED into unstable rygel_0.42.0-2_source.changes ACCEPTED into unstable I'll try to poke caja-extensions maintainers to see if they want to upload to unstable (but since I haven't heard anything so far I'll probably go ahead and NMU it again to unstable tomorrow). I've also filed RM bugs for dleyna-* see: #1023131 #1023133 #1023134 #1023135 I've poked the librm bug report again and raised severity to serious. Please consider removing librm (+ roger-router) from testing when it's the only remaining blocker for finishing the transition. Regards, Andreas Henriksson
Bug#940350: transition: libgweather
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Control: forwarded -1 https://release.debian.org/transitions/html/auto-libgweather.html Dear release team, I'm requesting a transition slot for libgweather on behalf of the Debian GNOME Team. >From libgweather NEWS: > This version of the library bumps the soname after an ABI break in 3.28.0 > that went unnoticed. If you see strange crashes, make sure to bump the > required version of libgweather to 3.28.0 or newer. In other words we should already be affected by the "new" ABI/API and no issues should arise. This transition is mainly to get the new version into unstable and sync SONAME with upstream. For avoidance of doubt I went ahead and did a rebuild of all reverse dependencies anyway and no issues where spotted. (For anyone interested the build logs temporarily available at: http://fatal.se/tmp/libgweather3.33.92/build-logs/ .. as attaching them did not work because of size.) Ben file: title = "libgweather"; is_affected = .depends ~ "libgweather-3-15" | .depends ~ "libgweather-3-16"; is_good = .depends ~ "libgweather-3-16"; is_bad = .depends ~ "libgweather-3-15"; Regards, Andreas Henriksson
Bug#933548: transition: gnome-desktop3
Control: tags -1 - moreinfo Dear release team, I've done rebuild tests of reverse dependencies for the gnome-desktop3 transition and the results are that there's one failure: budge-desktop (The build logs are temprorarily available from: https://fatal.se/tmp/gnome-desktop-3_3.34/build-logs/ ) It seems there's a version of budge-desktop prepared in experimental that adresses the problem. This transition should thus hopefully be in good shape and ready to go at any point when the release team have a slot free for it. Regards, Andreas Henriksson
Bug#933577: transition: evolution-data-server
FWIW The blocker for the evolution-data-server transition already identified by Laney could possibly be handled by temporarily removing src:eweouz from testing as it doesn't seem to have any reverse (build-)dependencies. (A full rebuild of reverse dependencies might however be useful to make sure no new issues has appeared since this bug was originally filed.) Regards, Andreas Henriksson
Bug#940460: transition: mutter
Package: release.debian.org Severity: normal Tags: moreinfo User: release.debian@packages.debian.org Usertags: transition Control: block -1 by 940161 933548 Control: forwarded -1 https://release.debian.org/transitions/html/auto-mutter.html Dear release team, I'm filing this bug report on behalf of the Debian Gnome Team to track the status of the upcoming mutter transition that's not yet quite ready to go (and thus tagged moreinfo). Depends: gsettings-desktop-schemas-dev (>= 3.33.0) - needs to be uploaded at the same time as mutter 3.34 Depends: libglib2.0-dev (>= 2.61.1) - upload to unstable tracked in https://bugs.debian.org/940161 Depends: libgnome-desktop-3-dev (>= 3.33.4) - transition tracked in https://bugs.debian.org/933548 Regards, Andreas Henriksson
Bug#933548: transition: gnome-desktop3
Hello, Adding a bunch of CCs for usual suspects as it seems noone got a copy of the go-ahead. On Sun, Sep 29, 2019 at 09:42:12PM +0200, Paul Gevers wrote: > Control: tags -1 confirmed [...] > Let's get on with this. Laney pointed out that to do gnome-desktop3 standalone we'd need this patch: https://gitlab.gnome.org/GNOME/gnome-shell/commit/f9a7718dda9641bf3750faba789edd701dfff5da >From #debian-release : elbrus: hi. Would it be ok to entagle some of the gnome transitions? eg. atleast mutter/gnome-shell and gnome-desktop3 together. Otherwise we'll need sourceful uploads to make old gnome-shell work with new gnome-desktop3 (and who knows what else) ah: yes that should be fine I'm thus thinking about doing this (unless someone else volunteers): * upload glib2.0 to unstable (to unblock mutter) * upload gnome-desktop3, mutter and gnome-shell * Ask bungie-desktop people to upload their exp version to unstable. If anyone thinks there's a reason to do anything differently, please speak up ASAP! Regards, Andreas Henriksson
Bug#933548: transition: gnome-desktop3
On Mon, Sep 30, 2019 at 01:39:36PM +0200, Emilio Pozuelo Monfort wrote: [...] > > I'm thus thinking about doing this (unless someone else volunteers): > > * upload glib2.0 to unstable (to unblock mutter) > > * upload gnome-desktop3, mutter and gnome-shell > > * Ask bungie-desktop people to upload their exp version to unstable. > > > > If anyone thinks there's a reason to do anything differently, please > > speak up ASAP! > > Yes, let's do all these (e-d-s, gnome-desktop3, mutter, and even libgweather > if > the rdeps are fine with that) as we have done in the past. I built my way up to gnome-shell and it looked like this: glib2.0, gsettings-desktop-schemas, gnome-desktop3, mutter, evolution-data-server, gobject-introspection, gjs, gnome-shell I went ahead and uploaded those now. Will investigate and follow up with surrounding sourceful uploads as needed. Regards, Andreas Henriksson
Bug#933577: transition: evolution-data-server
Hello, On Sun, Sep 29, 2019 at 10:02:39PM +0200, Paul Gevers wrote: > Control: tags -1 - moreinfo [...] > I just ACK'ed the gnome-desktop3 transition, so let's wait until that > migrates. In the mean time, please bump the severity of the FTBFS bug. As discussed in gnome-desktop3 bug report with pochu we started them all at once. Here's a status update for the sourceful uploads I've taken care of as a followup to starting this transition: bijiben uploaded gnome-todo uploaded evolution uploaded evolution-ews uploaded evolution-rss uploaded gnome-calendar previously mistakenly uploaded, building it seems to have woken up by itself. almanah needs exp -> unstable upload (can be temp removed from testing?!) folks needs exp -> unstable upload (zeitgeist issues on some archs needs investigations) gnome-contacts needs upload but blocked by folks eweouz needs patch in bts applied and uploaded. (can be temp removed from testing?!) abiword ... libreoffice Regards, Andreas Henriksson
Bug#933548: transition: gnome-desktop3
Control: block 933548 by 941467 Another status update regarding gnome 3.34 transitions. Issues: - DONE: glib2.0 failed on i386 and s390x, but give-backs was used to work around it. Needs to be investigated in detail later. Not a blocker for now. - how to handle folks is being discussed. Suggestion is to update zeitgeist (orphaned) and disable zeitgeist integration in folks (temporarily or permanently?) in folks. This will unblock folks and gnome-contacts. - samba FTBFS in unstable is a blocker for gnome-control-center builds. (See blocker above for bug report.) Sourceful uploads: - gnome-panel and gnome-flashback needs uploads (asked mitya57) BinNMUs: I think we should be ready to start a round of binnmus related to gnome-desktop3 transition, please schedule these: cheese eog gnome-clocks gnome-font-viewer gnome-screensaver gnome-software nautilus totem ukwm evince Possibly also: gnome-books and gnome-documents A short note about the eds transition: - abiword built here, can it be binNMUed? - Just sent a mail to libreoffice@p.d.o to make them aware of the ongoing transition and ask for their input. - (again: folks) - (also: gnome-panel and gnome-contacts) - These should be possible to handle via temporary removal from testing if needed: eweouz, glabels, gnome-phone-manager Regards, Andreas Henriksson
Bug#933548: transition: gnome-desktop3
On Wed, Oct 02, 2019 at 08:46:50PM -0400, Jeremy Bicha wrote: > There are also several autopkgtest failures triggered by glib2.0 and > gobject-introspection. I quickly looked over these and it seems they're all except one related to compiling stuff with -Werror. Mostly because of using GTime and/or GTimeVal which is deprecated. The odd one out is libgtk2-perl which fails test 44: [...] ok 38 ok 39 - 'new_from_xpm_data' isa 'Gtk2::Gdk::Pixbuf' ok 40 ok 41 ok 42 GdkPixbuf [ warning ] Inline XPM data is broken: Cannot read XPM colormap ok 43 - Don't crash on broken pixmap data GdkPixbuf [ warning ] Inline XPM data is broken: Invalid XPM header not ok 44 - Don't crash on partial pixmap data # Failed test 'Don't crash on partial pixmap data' # at t/GdkPixbuf.t line 126. ok 45 - 'new_from_data' isa 'Gtk2::Gdk::Pixbuf' ok 46 ok 47 ok 48 [...] The one not related to GTime / GTimeVal is dbus-test-runner: [...] /bin/bash ../libtool --tag=CC --mode=link gcc -pthread -I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -Werror -g -O2 -fdebug-prefix-map=/tmp/autopkgtest-lxc.ftgi3a2g/downtmp/build.NS5/src=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -o test-own-name test_own_name-test-own-name.o -lgio-2.0 -ldbus-glib-1 -ldbus-1 -lgobject-2.0 -lglib-2.0 test-libdbustest-mock.c: In function ‘test_signals’: test-libdbustest-mock.c:392:13: error: g_main_context_pending [-Werror] 392 | while (g_main_pending()) | ^ test-libdbustest-mock.c:393:13: error: g_main_context_iteration [-Werror] 393 | g_main_iteration(TRUE); | ^ test-libdbustest-mock.c:413:13: error: g_main_context_pending [-Werror] 413 | while (g_main_pending()) | ^ test-libdbustest-mock.c:414:13: error: g_main_context_iteration [-Werror] 414 | g_main_iteration(TRUE); | ^ [...] Regards, Andreas Henriksson
Bug#942428: transition: gssdp/gupnp
Package: release.debian.org Severity: normal Tags: moreinfo User: release.debian@packages.debian.org Usertags: transition Hello! The gssdp and gupnp transitions are best done together. The transition has previously been discussed a bit on IRC but I'm filing this for tracking purposes for getting the final blockers ironed out. As the dev packages have changed names libg(ssdp|upnp)-1.0-dev to libg(ssdp|upnp)-1.2-dev the entire transition will need sourceful uploads. Most reverse dependencies has already been prepared in experimental. Here are the affected packages and their status: $ (reverse-depends -r testing -b src:gssdp -l && reverse-depends -r testing -b src:gupnp -l ) | sort -u caja-extensions - #942343 fixed-upstream <--- NMU? dleyna-core - fixed in experimental dleyna-renderer - fixed in experimental dleyna-server - fixed in experimental gupnp - fixed in experimental gupnp-igd - exp FTBFS on armel, tests hangs <--- blocker? gupnp-tools - fixed in experimental peony-extensions - no rdeps, unmaintained <--- temporary removal? rygel - fixed in experimental upnp-router-control - no rdeps, unmaintained for years <-- permament removal? The final real blocker as I can see it is the gupnp-igd armel FTBFS. The problem is 100% reproducible on abel porterbox. The tests that hangs are the final two: test_gupnp_simple_igd_invalid_ip test_gupnp_simple_igd_empty_ip According to gdb the main thread is hanging in g_object_unref (igd) that's called last in the test functions. Since there's no obvious solution to this and I'm not going to invest (more) time into it nor to track down anyone who cares about armel issues I'm leaving this here as tagged moreinfo until someone has a plan for how the transition can happen. Regards, Andreas Henriksson
Bug#984925: pre-approval: updating python-networkmanager to 2.2 (bugfix release) in bullseye
RUE = 1 +NM_MANAGER_RELOAD_FLAG_NONE = 0 +NM_MANAGER_RELOAD_FLAG_CONF = 1 +NM_MANAGER_RELOAD_FLAG_DNS_RC = 2 +NM_MANAGER_RELOAD_FLAG_DNS_FULL = 4 +NM_MANAGER_RELOAD_FLAG_ALL = 7 +NM_DEVICE_INTERFACE_FLAG_NONE = 0 +NM_DEVICE_INTERFACE_FLAG_UP = 1 +NM_DEVICE_INTERFACE_FLAG_LOWER_UP = 2 +NM_DEVICE_INTERFACE_FLAG_CARRIER = 65536 +NM_CLIENT_PERMISSION_NONE = 0 +NM_CLIENT_PERMISSION_ENABLE_DISABLE_NETWORK = 1 +NM_CLIENT_PERMISSION_ENABLE_DISABLE_WIFI = 2 +NM_CLIENT_PERMISSION_ENABLE_DISABLE_WWAN = 3 +NM_CLIENT_PERMISSION_ENABLE_DISABLE_WIMAX = 4 +NM_CLIENT_PERMISSION_SLEEP_WAKE = 5 +NM_CLIENT_PERMISSION_NETWORK_CONTROL = 6 +NM_CLIENT_PERMISSION_WIFI_SHARE_PROTECTED = 7 +NM_CLIENT_PERMISSION_WIFI_SHARE_OPEN = 8 +NM_CLIENT_PERMISSION_SETTINGS_MODIFY_SYSTEM = 9 +NM_CLIENT_PERMISSION_SETTINGS_MODIFY_OWN = 10 +NM_CLIENT_PERMISSION_SETTINGS_MODIFY_HOSTNAME = 11 +NM_CLIENT_PERMISSION_SETTINGS_MODIFY_GLOBAL_DNS = 12 +NM_CLIENT_PERMISSION_RELOAD = 13 +NM_CLIENT_PERMISSION_CHECKPOINT_ROLLBACK = 14 +NM_CLIENT_PERMISSION_ENABLE_DISABLE_STATISTICS = 15 +NM_CLIENT_PERMISSION_ENABLE_DISABLE_CONNECTIVITY_CHECK = 16 +NM_CLIENT_PERMISSION_WIFI_SCAN = 17 +NM_CLIENT_PERMISSION_LAST = 17 +NM_CLIENT_PERMISSION_RESULT_UNKNOWN = 0 +NM_CLIENT_PERMISSION_RESULT_YES = 1 +NM_CLIENT_PERMISSION_RESULT_AUTH = 2 +NM_CLIENT_PERMISSION_RESULT_NO = 3 NM_VPN_SERVICE_STATE_UNKNOWN = 0 NM_VPN_SERVICE_STATE_INIT = 1 NM_VPN_SERVICE_STATE_SHUTDOWN = 2 diff --git a/ci/python-networkmanager.yml b/ci/python-networkmanager.yml new file mode 100644 index 000..f806955 Regards, Andreas Henriksson PS. Many thanks for making sure we go into hard-freeze with a reasonable amount of (not -ignore tagged) RC bug reports this time around! Really refreshing to atleast read that you're attempting to shorten the freeze!
Bug#984925: pre-approval: updating python-networkmanager to 2.2 (bugfix release) in bullseye
Control: block 984983 by 984925 Hello, I've done detailed investigations and reported them in a bug report against python3-networkmanager in https://bugs.debian.org/984925 I've also locally updated the package and verified that 2.2 solves the problem. I'm ready to pull the trigger and upload when/if you say so. (Have not yet pushed to the git repository since it includes reverting a pending compat bump, which we only want to do if we're uploading this during freeze. Can push on request if is interested.) Regards, Andreas Henriksson
Bug#853469: unblock: libarchive/3.2.1-6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libarchive
Fixes CVE-2017-5601 by cherry-picking a single upstream commit.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853278
unblock libarchive/3.2.1-6
-- System Information:
Debian Release: 9.0
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index e1386ce6..289df2d0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+libarchive (3.2.1-6) unstable; urgency=medium
+
+ * Add
debian/patches/Fail-with-negative-lha-compsize-in-lha_read_file_header_1.patch
+- Cherry-pick upstream commit 98dcbbf0bf4854bf987557
+ "Fail with negative lha->compsize in lha_read_file_header_1()"
+ Secunia SA74169, CVE-2017-5601 (Closes: #853278)
+
+ -- Andreas Henriksson Tue, 31 Jan 2017 10:25:56 +0100
+
libarchive (3.2.1-5) unstable; urgency=medium
* Cherry-pick upstream commits 7f17c791, eec077f5, e37b620f
diff --git
a/debian/patches/Fail-with-negative-lha-compsize-in-lha_read_file_header_1.patch
b/debian/patches/Fail-with-negative-lha-compsize-in-lha_read_file_header_1.patch
new file mode 100644
index ..3b35e267
--- /dev/null
+++
b/debian/patches/Fail-with-negative-lha-compsize-in-lha_read_file_header_1.patch
@@ -0,0 +1,23 @@
+From: Martin Matuska
+Date: Thu, 19 Jan 2017 22:00:18 +0100
+Subject: Fail with negative lha->compsize in lha_read_file_header_1() Fixes a
+ heap buffer overflow reported in Secunia SA74169
+
+---
+ libarchive/archive_read_support_format_lha.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/libarchive/archive_read_support_format_lha.c
b/libarchive/archive_read_support_format_lha.c
+index c359d83e..1a5617fa 100644
+--- a/libarchive/archive_read_support_format_lha.c
b/libarchive/archive_read_support_format_lha.c
+@@ -924,6 +924,9 @@ lha_read_file_header_1(struct archive_read *a, struct lha
*lha)
+ /* Get a real compressed file size. */
+ lha->compsize -= extdsize - 2;
+
++ if (lha->compsize < 0)
++ goto invalid; /* Invalid compressed file size */
++
+ if (sum_calculated != headersum) {
+ archive_set_error(&a->archive, ARCHIVE_ERRNO_MISC,
+ "LHa header sum error");
diff --git a/debian/patches/series b/debian/patches/series
index 24a6b0a7..68f4950f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -11,3 +11,4 @@ Correct-the-usage-of-PATH_MAX-as-reported-in-Issue-744.patch
Issue-761-Heap-overflow-reading-corrupted-7Zip-files.patch
Issue-747-and-others-Avoid-OOB-read-when-parsing-multiple.patch
Issue-767-Buffer-overflow-printing-a-filename.patch
+Fail-with-negative-lha-compsize-in-lha_read_file_header_1.patch
Re: Draft for taging 32 RC bugs with can-defer, will-remove or is-blocker
Hi Niels, On Sat, Jan 28, 2017 at 01:20:00PM +, Niels Thykier wrote: [...] > > 851819 flashplugin-nonfree will-remove ERROR: wget failed to > > download http://people.debian.org/~bartm/... [...] While I'm usually quite keen on removals, I'd suggest this one can be a "can-defer". The downloader itself seems to still be working all that's needed is a new signature for the new adobe release. AIUI this doesn't even involve touching the package, only dropping the signature in bartm's public_html on people.debian.org. This can be done at any time to fix the package during stretch lifetime. I guess the only reason this package is considered a key-package is because it's very popular among users, so would be quite unhelpful of us to remove it. Just my 5c Regards, Andreas Henriksson
Bug#810961: quvi, totem-pl-parser and cclive uploaded starting (and finishing?) the transition.
Hello release team! Just wanted to mention that I've uploaded libquvi-scripts, libquvi, quvi, totem-pl-parser to unstable as well as cclive to unstable via DELAYED/5. This starts the transition and hopefully once everything reaches the archive and builds on all architectures there should be no need for any binNMUs or anything like that since both the rdeps got sourceful uploads. Regards, Andreas Henriksson
Bug#812887: transition: iptables
Hello! On Sun, Feb 07, 2016 at 04:23:25PM +, Jonathan Wiltshire wrote: > On Wed, Jan 27, 2016 at 04:58:41PM +0100, Arturo Borrero Gonzalez wrote: > > iptables 1.6.0 has been released and we plan to include it in debian. > > > > The libxtables binary package name has been changed from libxtables10 to > > libxtables11. However, this change seems to affect very few packages (if > > any). > > > > Since an upload to experimental was done, a transition was set up [0]. > > Following the instructions [1] for transition, I've build-tested all > > reverse build-deps of iptables and they seem to build simply fine: > > > > * xtables-addons: no problems > > * connman: no problems > > * west-chamer: no problems > > > > So, I ask for a transition slot to upload iptables 1.6.0 to unstable. > > The transition completed. Please also binNMU iproute2 to build against the new libxtables and pick up a new recommends, or the 'ipt' module will be/stay broken. Regards, Andreas Henriksson
Bug#819979: transition: libgit2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-CC: Russell Sim , Pirate Praveen , Dmitry Smirnov Hello release team! I'd like to request a transition slot for libgit2. I've tested building reverse dependencies: birdfont cargo geany-plugins golang-git2go kate libgit2-glib python-pygit2 ruby-rugged geany-plugins already has a FTBFS bug reported at #819889 but I don't consider it a transition blocker as it has no reverse dependencies and could simply get temporarily removed from testing. The following failed to build with the new version and needs sourceful uploads: * libgit2-glib - I assumed this would simply be fixed by sourceful uploading of matching libgit2-glib v0.24.0, see #819871 * ruby-rugged - Pirate Praveen reported success with the new version he's prepared. So to summarize: RM geany-plugins sourceful uploads: libgit2-glib, ruby-rugged binNMU: birdfont, cargo, geany-plugins, golang-git2go, kate, python-pygit2 The new upstream release 0.24.0 was just uploaded to(wards) experimental (now stuck in NEW ofcourse) so an automatic tracker should be available soon. Ben file: title = "libgit2"; is_affected = .depends ~ "libgit2-23" | .depends ~ "libgit2-24"; is_good = .depends ~ "libgit2-24"; is_bad = .depends ~ "libgit2-23"; -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#819979: libgit2 transition pending, now in experimental.
Hello Dmitry, Pirate. The new libgit2 0.24.0 has just cleared NEW and should soon be available in the archive. If it has not yet reached your mirror I've put a copy of it at https://people.debian.org/~ah/libgit2/ for your convenience. It would be great if you could do an upload of your packages libgit2-glib / ruby-rugged for the new libgit2 targeted at experimental so we know all pieces are ready for the transition which is about to start. (We've got a go from the release team already!) For additional information the geany-plugins package FTBFS was just fixed and I tested it builds successfully against the new libgit2. This means all other packages affected by the libgit2 transition should be ready for binNMU once we kick off the transition by uploading libgit2 to unstable. If you need any help with getting your package ready please just shout! If you've got any suggestions for additional improvements of the libgit2 package please mention them. The NMU which Dmitry spotted was missed has now been incorporated with additional fixes. Your feedback is appreciated. Regards, Andreas Henriksson
Bug#819979: libgit2 transition pending, now in experimental.
Hello all again! On Mon, Apr 11, 2016 at 05:34:59PM +0200, Andreas Henriksson wrote: > Hello Dmitry, Pirate. > > The new libgit2 0.24.0 has just cleared NEW and should soon be available > in the archive. If it has not yet reached your mirror I've put a copy of > it at https://people.debian.org/~ah/libgit2/ for your convenience. > > It would be great if you could do an upload of your packages [...] Thanks to quick actions from Dmitry and Pirate everything is now available in experimental. I've just uploaded the new libgit2 to unstable kicking off this transition! Release team, please spin up the binNMUs for everything except libgit2-glib and ruby-rugged which will have sourceful uploads. (Please also note that geany-plugins FTBFS has just been fixed and have not yet transitioned to testing yet.) Dmitry, Pirate please upload your packages to unstable at your convenience. The auto tracker is now also available at: https://release.debian.org/transitions/html/auto-libgit2.html Regards, Andreas Henriksson
Bug#797074: libical2 transition
Control: retitle -1 transition: libical2 Hello release-team! A new upstream release of libical is out -> 2.0.0. This version comes with a new so name. I'm repurposing this old bug report, initially filed for the unfortunate and unexpected ABI breakage in 1.0.1, for the new version. A transition to newer libical is needed for updating evolution-data-server, et.al. Since I've heard no feedback since my last NMU, I've gone ahead and uploaded a package of the new version towards experimental. It's currently stuck in (binary-)NEW. I've build-tested reverse dependencies and came up with the following results: FAIL -- will need sourceful uploads. == ical2html-2.1 webcit-9.01-dfsg citadel-9.01 SUCCESS -- should be binNMUable. == jana-0.0.0+git20091215.9ec1da8a libsynthesis-3.4.0.47.5+syncevolution-1.5.1 orage-4.12.1 osmo-0.2.14 gnome-shell-3.20.1 gnome-todo-3.18.1 gnome-panel-3.18.2 gnome-calendar-3.20.1 gnokii-0.6.30+dfsg cairo-dock-plug-ins-3.4.0 bluez-5.36 bijiben-3.20.0 asterisk-13.7.2~dfsg almanah-0.11.1 agenda.app-0.42.2 syncevolution-1.4.99.4 abiword-3.0.1 evolution-ews-3.18.5 evolution-data-server-3.18.5 kdepimlibs-4.14.10 evolution-3.18.5.1 kmymoney-4.6.6 Build logs available at: https://people.debian.org/~ah/libical-transition/ (All three seems to fail on the same thing which hopefully means it's easy to fix: error: 'icalerror_errors_are_fatal' undeclared (first use in this function) icalerror_errors_are_fatal = 0; ) Once libical has cleared the NEW queue I'll file the bugs against the failing packages, set them as blockers for this bug and remove the moreinfo tag when it looks like we're ready to start the transition. Consider this a heads up warning. Regards, Andreas Henriksson
Bug#797074: libical2 transition ftbfs bugs now filed
Control: block -1 by 822565 822569 822572 Hello! The FTBFS bugs for the libical2 transition has now been filed including trivial patches for all of them. (Waiting for libical to get through binary-NEW and then likely follow up with an arm build fix before removing the moreinfo tag.) Regards, Andreas Henriksson
Bug#797074: libical2 transition now ready to start!
Control: tags -1 = The libical testsuite/FTBFS bugs should now be fixed in experimental and everything should be ready to go thus unsetting the morinfo tag. Please tell me once we ready to kick off this transition. (Sourceful uploads for the blocker bugs to experimental has not happened as fas as I'm aware, but as the patches are so trivial I think we can go straight to unstable with those.) Regards, Andreas Henriksson
Bug#797074: libical2 transition now ready to start!
Hello release team! On Tue, May 10, 2016 at 01:44:36PM +0200, Emilio Pozuelo Monfort wrote: > Control: tags -1 confirmed > > On 06/05/16 09:44, Andreas Henriksson wrote: > > Control: tags -1 = > > > > The libical testsuite/FTBFS bugs should now be fixed in experimental [...] > Go ahead. A quick followup from me to summarize where I think we are now: The new libical was uploaded and Emilio triggered binNMU for the packages which was suitable for that. They've now all built on all architectures. Some sourceful uploads where done despite the ongoing transition, for example gnome-todo, gnome-calendar. Also the required sourceful uploads of citadel and webcit just happened. All of these might be useful to age. The remaining problematic packages which should be possible to handle via temporary removal from testing are syncevolution (#824426) and ical2html (#822565). If I've not made any mistakes as far as I see it you should now with some force be able to push things into testing and finalize the transition. Regards, Andreas Henriksson
Bug#797074: libical2 transition now ready to start!
On Mon, May 16, 2016 at 09:29:00PM +0200, Emilio Pozuelo Monfort wrote: > libical is already in testing. Oh! [...] > From your side it's all done now, so you can stop worrying about this. :) Great, thanks! :) Regards, Andreas Henriksson
Bug#859437: unblock: util-linux/2.29.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-CC: debian-b...@lists.debian.org Please consider unblocking package util-linux It contains many bugfixes cherry-picked from the master branch, not very exciting stuff, fixes CVE-2017-2616 but since we don't build su from util-linux (yet) it's also *YAWN*. I've received no (negative) feedback since the upload. unblock util-linux/2.29.2-1
Bug#859437: unblock: util-linux/2.29.2-1
Hi, On Mon, Apr 03, 2017 at 10:52:13PM +0200, Cyril Brulebois wrote: > No objections based on a quick read of the changelog, beware of “PT” > (for GPT) in src/context.c and “entreis” (for entries) in src/gpt.c. As far as I can see PT (where used in code comments) are intentional meaning "(any kind of) partition table", ie. MBR or GPT (or both) not necessarily just GPT. If you think otherwise (and care to bother) please point out the exact error more clearly (because I might just be too tired to see it). I've notified upstream about the "entreis" debug message typo. (Spotted "memu" myself recently, which I mentioned and it was swiftly fixed in upstream master branch...) Thanks. Regards, Andreas Henriksson
Bug#859702: unblock: libarchive/3.2.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libarchive It's a new upstream "security release". (The one issue someone cared to file a CVE for was already cherry-picked into last upload that's currently in testing/stretch though.) It also "fixes" "serious" bug #859455 unblock libarchive/3.2.2-2 -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-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)
Bug#924394: unblock: libqmi/1.22.0-1.2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libqmi
The current version in Buster has incorrect "client id" tracking
and thus breaks things like ModemManagers ability to receive SMS
(and who known what else).
Upstream has released a one-line fix which is what I cherry-picked:
https://gitlab.freedesktop.org/mobile-broadband/libqmi/commit/78986d4df7865bb889e18a129a5f0f01ed7f3806
Debdiff attached.
unblock libqmi/1.22.0-1.2
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (400, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libqmi-1.22.0/debian/changelog libqmi-1.22.0/debian/changelog
--- libqmi-1.22.0/debian/changelog 2019-02-08 00:22:46.0 +0100
+++ libqmi-1.22.0/debian/changelog 2019-03-12 14:19:35.0 +0100
@@ -1,3 +1,11 @@
+libqmi (1.22.0-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add debian/patches/git_reset-offset-before-2nd-call.patch from upstream.
+- equivalent to 1.22.2 release except the broken manpages in that release.
+
+ -- Andreas Henriksson Tue, 12 Mar 2019 14:19:35 +0100
+
libqmi (1.22.0-1.1) unstable; urgency=medium
* Non-maintainer upload
diff -Nru libqmi-1.22.0/debian/patches/git_reset-offset-before-2nd-call.patch
libqmi-1.22.0/debian/patches/git_reset-offset-before-2nd-call.patch
--- libqmi-1.22.0/debian/patches/git_reset-offset-before-2nd-call.patch
1970-01-01 01:00:00.0 +0100
+++ libqmi-1.22.0/debian/patches/git_reset-offset-before-2nd-call.patch
2019-03-12 14:19:22.0 +0100
@@ -0,0 +1,25 @@
+From 78986d4df7865bb889e18a129a5f0f01ed7f3806 Mon Sep 17 00:00:00 2001
+From: Valentin Blot
+Date: Thu, 28 Feb 2019 13:08:50 +
+Subject: [PATCH] libqmi-glib,proxy: reset offset before 2nd call to
+ qmi_message_tlv_read_init
+
+---
+ src/libqmi-glib/qmi-proxy.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/libqmi-glib/qmi-proxy.c b/src/libqmi-glib/qmi-proxy.c
+index 00a1847..63e2ec1 100644
+--- a/src/libqmi-glib/qmi-proxy.c
b/src/libqmi-glib/qmi-proxy.c
+@@ -489,6 +489,7 @@ track_cid (Client *client,
+ if ((error_status != 0x00) || (error_code != QMI_PROTOCOL_ERROR_NONE))
+ return;
+
++offset = 0;
+ if (((init_offset = qmi_message_tlv_read_init (message,
QMI_MESSAGE_OUTPUT_TLV_ALLOCATION_INFO, NULL, &error)) == 0) ||
+ !qmi_message_tlv_read_guint8 (message, init_offset, &offset,
&service_tmp, &error) ||
+ !qmi_message_tlv_read_guint8 (message, init_offset, &offset,
&(info.cid), &error)) {
+--
+2.18.1
+
diff -Nru libqmi-1.22.0/debian/patches/series
libqmi-1.22.0/debian/patches/series
--- libqmi-1.22.0/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ libqmi-1.22.0/debian/patches/series 2019-03-12 14:19:28.0 +0100
@@ -0,0 +1 @@
+git_reset-offset-before-2nd-call.patch
Bug#926585: unblock: shishi/1.0.2-6.2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package shishi
unblock shishi/1.0.2-6.2
Fixes FTBFS.
Greetings from Gothenburg BSP.
diff -Nru shishi-1.0.2/debian/changelog shishi-1.0.2/debian/changelog
--- shishi-1.0.2/debian/changelog 2018-01-19 15:47:40.0 +0100
+++ shishi-1.0.2/debian/changelog 2019-04-07 13:26:04.0 +0200
@@ -1,3 +1,10 @@
+shishi (1.0.2-6.2) unstable; urgency=medium
+
+ * Non-maintainer upload with greeting from Gothenburg BSP.
+ * Add debian/patches/portability-changes.diff (Closes: #924123)
+
+ -- Andreas Henriksson Sun, 07 Apr 2019 13:26:04 +0200
+
shishi (1.0.2-6.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru shishi-1.0.2/debian/patches/portability-changes.diff
shishi-1.0.2/debian/patches/portability-changes.diff
--- shishi-1.0.2/debian/patches/portability-changes.diff1970-01-01
01:00:00.0 +0100
+++ shishi-1.0.2/debian/patches/portability-changes.diff2019-04-07
13:26:04.0 +0200
@@ -0,0 +1,67 @@
+From: Andreas Henriksson
+Subject: pam_shishi: Portability changes.
+
+This is the upstream commit
+http://git.savannah.gnu.org/gitweb/?p=shishi.git;a=commitdiff;h=07cd137bf79af3b9abfe08ff55c36a0c6785e733
+excluding white-space only changes (git diff -w), to make it minimal and
+easier for debian-release team to review.
+
+Addresses: https://bugs.debian.org/924123
+
+Index: shishi-1.0.2/extra/pam_shishi/pam_shishi.c
+===
+--- shishi-1.0.2.orig/extra/pam_shishi/pam_shishi.c
shishi-1.0.2/extra/pam_shishi/pam_shishi.c
+@@ -33,11 +33,6 @@
+
+ #include
+
+-/* Libtool defines PIC for shared objects */
+-#ifndef PIC
+-#define PAM_STATIC
+-#endif
+-
+ /* These #defines must be present according to PAM documentation. */
+ #define PAM_SM_AUTH
+ #define PAM_SM_ACCOUNT
+@@ -58,13 +53,13 @@
+ #define D(x) /* nothing */
+ #endif
+
++/* Rely on
++ * for settings in general, as PAM_EXTERN
++ * is not universal among PAM implementations.
++ */
+ #ifndef PAM_EXTERN
+-#ifdef PAM_STATIC
+-#define PAM_EXTERN static
+-#else
+-#define PAM_EXTERN extern
+-#endif
+-#endif
++# define PAM_EXTERN
++#endif /* !PAM_EXTERN */
+
+ PAM_EXTERN int
+ pam_sm_authenticate (pam_handle_t * pamh,
+@@ -287,6 +282,7 @@ pam_sm_chauthtok (pam_handle_t * pamh, i
+ return retval;
+ }
+
++/* Linux-PAM. */
+ #ifdef PAM_STATIC
+
+ struct pam_module _pam_shishi_modstruct = {
+@@ -299,4 +295,11 @@ struct pam_module _pam_shishi_modstruct
+ pam_sm_chauthtok
+ };
+
+-#endif
++#endif /* PAM_STATIC */
++
++/* OpenPAM */
++#ifdef PAM_MODULE_ENTRY
++
++PAM_MODULE_ENTRY("pam_shishi");
++
++#endif /* PAM_MODULE_ENTRY */
diff -Nru shishi-1.0.2/debian/patches/series shishi-1.0.2/debian/patches/series
--- shishi-1.0.2/debian/patches/series 2018-01-19 15:47:40.0 +0100
+++ shishi-1.0.2/debian/patches/series 2019-04-07 13:25:26.0 +0200
@@ -1,3 +1,4 @@
64bigendian-ftbfs.diff
fix_gcrypt_detection.diff
gtkdocize.diff
+portability-changes.diff
Bug#926597: unblock: golang-github-puerkitobio-purell/1.1.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Greetings from the Gothenburg BSP.
Please unblock package golang-github-puerkitobio-purell
unblock golang-github-puerkitobio-purell/1.1.0-2
Fixes FTBFS (testsuite failure)
(Sorry, this also included some minor trivial changes that where
already sitting in the salsa git repo for this package.)
Regards,
Andreas Henriksson
diff --git a/debian/changelog b/debian/changelog
index a85603e..e233aac 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+golang-github-puerkitobio-purell (1.1.0-2) unstable; urgency=medium
+
+ * Team upload with greetings from Gothenburg BSP.
+
+ [ Alexandre Viau ]
+ * Point Vcs-* urls to salsa.debian.org.
+
+ [ Andreas Henriksson ]
+ * Add debian/patches/pr-29.patch (Closes: #926380)
+
+ -- Andreas Henriksson Sun, 07 Apr 2019 17:00:51 +0200
+
golang-github-puerkitobio-purell (1.1.0-1) unstable; urgency=medium
* New upstream release
diff --git a/debian/control b/debian/control
index a6a5a13..ce8e849 100644
--- a/debian/control
+++ b/debian/control
@@ -1,6 +1,6 @@
Source: golang-github-puerkitobio-purell
Section: devel
-Priority: extra
+Priority: optional
Maintainer: Debian Go Packaging Team
Uploaders: Anthony Fok
Build-Depends: debhelper (>= 9),
@@ -9,10 +9,10 @@ Build-Depends: debhelper (>= 9),
golang-github-opennota-urlesc-dev (>=
0.0~git20150208.0.5fa9ff0-3),
golang-golang-x-net-dev,
golang-golang-x-text-dev
-Standards-Version: 3.9.8
+Standards-Version: 4.0.0
Homepage: https://github.com/PuerkitoBio/purell
-Vcs-Browser:
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-puerkitobio-purell.git
-Vcs-Git:
https://anonscm.debian.org/git/pkg-go/packages/golang-github-puerkitobio-purell.git
+Vcs-Browser:
https://salsa.debian.org/go-team/packages/golang-github-puerkitobio-purell
+Vcs-Git:
https://salsa.debian.org/go-team/packages/golang-github-puerkitobio-purell.git
XS-Go-Import-Path: github.com/PuerkitoBio/purell
Package: golang-github-puerkitobio-purell-dev
diff --git a/debian/copyright b/debian/copyright
index 707eab8..afd538d 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: Purell
Source: https://github.com/PuerkitoBio/purell
diff --git a/debian/gitlab-ci.yml b/debian/gitlab-ci.yml
new file mode 100644
index 000..5c8c31b
--- /dev/null
+++ b/debian/gitlab-ci.yml
@@ -0,0 +1,28 @@
+
+# auto-generated, DO NOT MODIFY.
+# The authoritative copy of this file lives at:
+# https://salsa.debian.org/go-team/ci/blob/master/cmd/ci/gitlabciyml.go
+
+# TODO: publish under debian-go-team/ci
+image: stapelberg/ci2
+
+test_the_archive:
+ artifacts:
+paths:
+- before-applying-commit.json
+- after-applying-commit.json
+ script:
+# Create an overlay to discard writes to /srv/gopath/src after the build:
+- "rm -rf /cache/overlay/{upper,work}"
+- "mkdir -p /cache/overlay/{upper,work}"
+- "mount -t overlay overlay -o
lowerdir=/srv/gopath/src,upperdir=/cache/overlay/upper,workdir=/cache/overlay/work
/srv/gopath/src"
+- "export GOPATH=/srv/gopath"
+- "export GOCACHE=/cache/go"
+# Build the world as-is:
+- "ci-build -exemptions=/var/lib/ci-build/exemptions.json >
before-applying-commit.json"
+# Copy this package into the overlay:
+- "GBP_CONF_FILES=:debian/gbp.conf gbp buildpackage --git-no-pristine-tar
--git-ignore-branch --git-ignore-new --git-export-dir=/tmp/export
--git-no-overlay --git-tarball-dir=/nonexistant --git-cleaner=/bin/true
--git-builder='dpkg-buildpackage -S -d --no-sign'"
+- "pgt-gopath -dsc /tmp/export/*.dsc"
+# Rebuild the world:
+- "ci-build -exemptions=/var/lib/ci-build/exemptions.json >
after-applying-commit.json"
+- "ci-diff before-applying-commit.json after-applying-commit.json"
diff --git a/debian/patches/pr-29.patch b/debian/patches/pr-29.patch
new file mode 100644
index 000..c5f889e
--- /dev/null
+++ b/debian/patches/pr-29.patch
@@ -0,0 +1,76 @@
+From b5f01560a83bfe6f1551df3579f2149ae7f3f54c Mon Sep 17 00:00:00 2001
+From: Martin Angers
+Date: Sat, 16 Feb 2019 16:08:08 -0500
+Subject: [PATCH] fix failing go1.12 test due to control chars causing
+ url.Parse to fail
+
+---
+ purell_test.go | 41 -
+ 1 file changed, 24 insertions(+), 17 deletions(-)
+
+diff --git a/purell_test.go b/purell_test.go
+index 8eb5191..efde722 100644
+--- a/purell_test.go
b/purell_test.go
+@@ -4,6 +4,7 @@ import (
+ "fmt"
+ "net/url"
+ "testing"
++ "unicode"
+ )
+
+ type testCase s
fix neomutt gpg integration NMU/pre-approval
Control: tags -1 + patch Hello all, Please see attached debdiff fixing this issue, unbreaking gpg integration (by using the same libexecdir as upstream expects which is also the default in dh compat >= 12 but avoiding to bump compat now to hopefully get an easier freeze exception). I personally find gpg integration very important for this application in particular (neomutt), so. release-team: can I get a pre-approval for this? Regards, Andreas Henriksson PS. This message sent gpg-signed from neomutt with proposed changes. diff -Nru neomutt-20180716+dfsg.1/debian/changelog neomutt-20180716+dfsg.1/debian/changelog --- neomutt-20180716+dfsg.1/debian/changelog2018-07-18 23:15:56.0 +0200 +++ neomutt-20180716+dfsg.1/debian/changelog2019-04-10 08:34:57.0 +0200 @@ -1,3 +1,12 @@ +neomutt (20180716+dfsg.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Use /usr/libexec as libexecdir (Closes: #905159) +(dh compat >= 12 does the right thing, so once bumped then +--libexecdir can be dropped from debian/rules.) + + -- Andreas Henriksson Wed, 10 Apr 2019 08:34:57 +0200 + neomutt (20180716+dfsg.1-1) unstable; urgency=medium * New upstream release. diff -Nru neomutt-20180716+dfsg.1/debian/neomutt.install neomutt-20180716+dfsg.1/debian/neomutt.install --- neomutt-20180716+dfsg.1/debian/neomutt.install 2018-03-04 15:34:47.0 +0100 +++ neomutt-20180716+dfsg.1/debian/neomutt.install 2019-04-10 08:34:57.0 +0200 @@ -1,11 +1,11 @@ debian/tmp/usr/bin/neomutt debian/tmp/usr/share/locale/* -debian/tmp/usr/lib/neomutt/*usr/lib/neomutt -debian/extra/lib/mailspell usr/lib/neomutt -debian/extra/lib/source-neomuttrc.dusr/lib/neomutt -debian/extra/lib/debian-ldap-query usr/lib/neomutt -debian/extra/lib/mailto-neomutt usr/lib/neomutt +debian/tmp/usr/libexec/neomutt/* usr/libexec/neomutt +debian/extra/lib/mailspell usr/libexec/neomutt +debian/extra/lib/source-neomuttrc.dusr/libexec/neomutt +debian/extra/lib/debian-ldap-query usr/libexec/neomutt +debian/extra/lib/mailto-neomuttusr/libexec/neomutt debian/tmp/neomuttrc etc contrib/gpg.rc etc/neomuttrc.d diff -Nru neomutt-20180716+dfsg.1/debian/rules neomutt-20180716+dfsg.1/debian/rules --- neomutt-20180716+dfsg.1/debian/rules2018-05-27 17:15:30.0 +0200 +++ neomutt-20180716+dfsg.1/debian/rules2019-04-10 08:31:38.0 +0200 @@ -24,7 +24,7 @@ override_dh_auto_configure: dh_auto_configure -- \ --mandir=/usr/share/man \ - --libexecdir=/usr/lib \ + --libexecdir=/usr/libexec \ --with-mailpath=/var/mail \ --gpgme \ --lua \ signature.asc Description: PGP signature
Bug#795911: Upload of gtk+3.0/3.14.5-1+deb8u1 to Jessie will be accepted by the Stable Release Managers
Hello Ruben Undheim.
I've uploaded gtk+3.0/3.14.5-1+deb8u1 now. Please finish things up
with the release team to get it accepted. Some more details below.
On Wed, Aug 19, 2015 at 12:25:53AM +0200, Ruben Undheim wrote:
>
> I checked the svn repo. Revision r43867 seems to be the "golden" Jessie
> commit.
> (svn://anonscm.debian.org/pkg-gnome/desktop/unstable/gtk+3.0/)
Fwiw, we tag every upload ... so if there's not already a jessie branch
for the module you're changing then easiest is to copy the tag into
a branch. I did it like this:
svn cp svn+ssh://svn.debian.org/svn/pkg-gnome/tags/gtk+3.0/3.14.5-1/
svn+ssh://svn.debian.org/svn/pkg-gnome/desktop/jessie/gtk+3.0/
>
> I have attached a patch here that applies to that svn revision with the
> changes.
> Hopefully that can save you some time.
>
Yes, thanks. I imported your patch and did a few very minor tweaks mostly
to better track patch origins with more details. Final/uploaded diff
attached. Generated via:
svn diff svn+ssh://svn.debian.org/svn/pkg-gnome/tags/gtk+3.0/3.14.5-1
svn+ssh://svn.debian.org/svn/pkg-gnome/tags/gtk+3.0/3.14.5-1+deb8u1
Regards,
Andreas Henriksson
svn diff svn+ssh://svn.debian.org/svn/pkg-gnome/tags/gtk+3.0/3.14.5-1 svn+ssh://svn.debian.org/svn/pkg-gnome/tags/gtk+3.0/3.14.5-1+deb8u1
Index: debian/patches/074_fix_freeze_while_resume_events.patch
===
--- debian/patches/074_fix_freeze_while_resume_events.patch (.../3.14.5-1) (revision 0)
+++ debian/patches/074_fix_freeze_while_resume_events.patch (.../3.14.5-1+deb8u1) (revision 45696)
@@ -0,0 +1,59 @@
+Description: This patch fixes a bug causing gtk applications to freeze
+ every now and then.
+ .
+ It deserves to be applied in Jessie because the bug will and has caused users
+ to lose their work. One common consequence of the bug is that all open
+ gnome-terminal instances may suddenly crash at the same time.
+Author: Ruben Undheim
+Bug-Debian: https://bugs.debian.org/787419
+Origin: https://git.gnome.org/browse/gtk+/commit/?id=ff256956 + https://git.gnome.org/browse/gtk+/commit/?id=561ff51a
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=742636
+Last-Update: 2015-08-17
+
+Index: gtk+3.0-3.14.5/gdk/gdkinternals.h
+===
+--- gtk+3.0-3.14.5.orig/gdk/gdkinternals.h
gtk+3.0-3.14.5/gdk/gdkinternals.h
+@@ -240,6 +240,7 @@ struct _GdkWindow
+ guint in_update : 1;
+ guint geometry_dirty : 1;
+ guint event_compression : 1;
++ guint frame_clock_events_paused : 1;
+
+ /* The GdkWindow that has the impl, ref:ed if another window.
+* This ref is required to keep the wrapper of the impl window alive
+Index: gtk+3.0-3.14.5/gdk/gdkwindow.c
+===
+--- gtk+3.0-3.14.5.orig/gdk/gdkwindow.c
gtk+3.0-3.14.5/gdk/gdkwindow.c
+@@ -10603,6 +10603,8 @@ gdk_window_flush_events (GdkFrameClock *
+ _gdk_display_pause_events (display);
+
+ gdk_frame_clock_request_phase (clock, GDK_FRAME_CLOCK_PHASE_RESUME_EVENTS);
++
++ window->frame_clock_events_paused = TRUE;
+ }
+
+ static void
+@@ -10629,6 +10631,8 @@ gdk_window_resume_events (GdkFrameClock
+
+ display = gdk_window_get_display (window);
+ _gdk_display_unpause_events (display);
++
++ window->frame_clock_events_paused = FALSE;
+ }
+
+ static void
+@@ -10661,6 +10665,9 @@ gdk_window_set_frame_clock (GdkWindow
+
+ if (window->frame_clock)
+ {
++ if (window->frame_clock_events_paused)
++ gdk_window_resume_events (window->frame_clock, G_OBJECT (window));
++
+ g_signal_handlers_disconnect_by_func (G_OBJECT (window->frame_clock),
+ G_CALLBACK (gdk_window_flush_events),
+ window);
+
+
+
Index: debian/patches/081_fix_huge_icons.patch
===
--- debian/patches/081_fix_huge_icons.patch (.../3.14.5-1) (revision 0)
+++ debian/patches/081_fix_huge_icons.patch (.../3.14.5-1+deb8u1) (revision 45696)
@@ -0,0 +1,36 @@
+Description: Backporting a fix for a bug which cause trouble with icon sizes
+ in GTK applications
+ .
+ It deserves to be applied in Jessie mainly because the bug is quite annoying
+ and the fix is very small and hence little chance of any regression.
+Author: Ruben Undheim
+Bug-Debian: https://bugs.debian.org/773135
+Origin: https://git.gnome.org/browse/gtk%2B/commit/?id=b44df22
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=741259
+Last-Update: 2015-08-17
+
+Index: gtk-bugfix/gtk/deprecated/gtkimagemenuitem.c
+===
+--- gtk-bugfix.orig/gtk/deprecated/gtkimagemenuitem.c
gtk-bugfix/gtk/deprecated/gtkimagemenuitem.c
+@@ -1099,6 +1099,8 @@ gtk_image_menu_item_set_image (GtkImageM
+ "no-show-all",
Bug#797074: transition: libical
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello. I've already updated the libical package to a new upstream micro-release. Given that this was a micro-release plus the following release note I did not expect any breakage: "Version 1.0.1 fixes some bugs and adds some small features to version 1.0.0 while retaining binary and source compatibility." Unfortunately this seems to not be true. While there where no missing symbols there are apparently other ABI breakages as reported in https://bugs.debian.org/797003 Not sure about the full reasons for the breakage but it looks to me like it's partially caused by a debian patch to generate reproducible builds which sorts the output of a generated enum which means new additions ends up in the middle instead of at the end. Will this patch cause ABI problems for every new release from now on I wonder?! This might not be the only reason for breakage though and I've only quickly looked at it. Anyway, back to the current breakage. The last time similar breakage was upon us, we seem to simply have renamed the package and then rebuilt reverse dependencies. Please advice if you'd like me to upload a new version with libical1a renamed to libical1b and start a transition Ben file: title = "libical"; is_affected = .depends ~ "libical1a" | .depends ~ "libical1b"; is_good = .depends ~ "libical1b"; is_bad = .depends ~ "libical1a"; -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#797074: transition: libical
Hello Julien Cristau.
Thanks for your quick reply.
On Thu, Aug 27, 2015 at 06:17:22PM +0200, Julien Cristau wrote:
> I'd prefer to fix the root cause and start by making sure no accidental
> ABI breakage like this happens again. Then we can talk about whether
> the ABI is the libical1a one or something else.
I'd like to avoid being held responsible for the root cause of this as
it's a sin from the past (see comment #27 in bug #773916), but I've
added a check to avoid having the next person fall into the same
pitfall Hopefully this is good enough for now? (See below.)
Regards,
Andreas Henriksson
(Removed boring parts from diff where debian/libical1a.* where
renamed to debian/libical1b.* ...)
diff -Nru libical-1.0.1/debian/changelog libical-1.0.1/debian/changelog
--- libical-1.0.1/debian/changelog 2015-08-19 19:27:43.0 +0200
+++ libical-1.0.1/debian/changelog 2015-08-27 19:24:00.0 +0200
@@ -1,3 +1,15 @@
+libical (1.0.1-0.2) UNRELEASED; urgency=medium
+
+ * Rename libical1a to libical1b as every update to generated API
+from design-data/*.csv causes subtle ABI breakage. (Closes: #797003)
+(See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773916#27
+ for further background on this issue.)
+ * Add build-time check in debian/rules to catch future mistakes
+by running md5sum check on the design-data/*.csv files and
+generate an error message when they have changed.
+
+ -- Andreas Henriksson Thu, 27 Aug 2015 19:17:37 +0200
+
libical (1.0.1-0.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru libical-1.0.1/debian/control libical-1.0.1/debian/control
--- libical-1.0.1/debian/control2015-01-03 14:58:53.0 +0100
+++ libical-1.0.1/debian/control2015-08-27 19:16:48.0 +0200
@@ -9,18 +9,18 @@
Package: libical-dev
Section: libdevel
Architecture: any
-Depends: libical1a (= ${binary:Version}), ${misc:Depends}
+Depends: libical1b (= ${binary:Version}), ${misc:Depends}
Description: iCalendar library implementation in C (development)
libical is an open source implementation of the IETF's iCalendar calendaring
and scheduling protocols (RFC 2445, 2446, and 2447). It parses iCal components
and provides a C API for manipulating the component properties, parameters,
and subcomponents.
-Package: libical1a
+Package: libical1b
Architecture: any
Depends: tzdata, ${misc:Depends}, ${shlibs:Depends}
-Breaks: libical1
-Replaces: libical1
+Breaks: libical1, libical1a
+Replaces: libical1, libical1a
Description: iCalendar library implementation in C (runtime)
libical is an open source implementation of the IETF's iCalendar calendaring
and scheduling protocols (RFC 2445, 2446, and 2447). It parses iCal components
@@ -34,7 +34,7 @@
Priority: extra
Architecture: any
Section: debug
-Depends: libical1a (= ${binary:Version}), ${misc:Depends}
+Depends: libical1b (= ${binary:Version}), ${misc:Depends}
Description: debugging symbols for libical
This package contains the debugging symbols associated with libical.
.
diff -Nru libical-1.0.1/debian/generated-abi-check.md5sum
libical-1.0.1/debian/generated-abi-check.md5sum
--- libical-1.0.1/debian/generated-abi-check.md5sum 1970-01-01
01:00:00.0 +0100
+++ libical-1.0.1/debian/generated-abi-check.md5sum 2015-08-27
19:14:04.0 +0200
@@ -0,0 +1,4 @@
+ecef3fdcdd016fddbef023b3f4d111bf design-data/parameters.csv
+3f782626dea89516e773365745f095ea design-data/properties.csv
+4f92462d77b9c394633616711ccd21e6 design-data/restrictions.csv
+27cd5b5f7c8e1c60a18a4ec285910caa design-data/value-types.csv
diff -Nru libical-1.0.1/debian/libical1a.docs
libical-1.0.1/debian/libical1a.docs
diff -Nru libical-1.0.1/debian/libical1a.install
libical-1.0.1/debian/libical1a.install
diff -Nru libical-1.0.1/debian/libical1a.symbols
libical-1.0.1/debian/libical1a.symbols
diff -Nru libical-1.0.1/debian/rules libical-1.0.1/debian/rules
--- libical-1.0.1/debian/rules 2015-01-03 14:58:53.0 +0100
+++ libical-1.0.1/debian/rules 2015-08-27 19:28:08.0 +0200
@@ -2,3 +2,13 @@
%:
dh $@ --buildsystem=cmake --parallel --list-missing
--dbg-package=libical-dbg
+
+override_dh_auto_test:
+ md5sum --status -c debian/generated-abi-check.md5sum || (echo "ERROR:
Generated ABI was changed and will cause subtle ABI breakage. Please prepare
the package for library transition and update debian/generated-abi-check.md5sum
(see debian/rules for the source of this message.)" && exit 1)
+# when you got caught by the above check, do this:
+# rename the package in debian/control from libical1x to libical1y
+# (and do the same for libical1x* files under debian/).
+# update debian/generated-abi-check.md5sum by running:
+# for a in design-data/*.csv ; do md5sum $a ; done > \
+# debian/generated-abi-check.md5sum
+# request a transition slot via "reportbug release.debian.org"
Bug#800599: transition: evolution-data-server 3.18
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello.
For updating evolution-data-server to 3.18.0 (as packaged in
experimental) a transition is needed.
There is already an auto tracker set up at:
https://release.debian.org/transitions/html/auto-evolution-data-server.html
I've rebuilt sid reverse build-dependencies (except libreoffice which is
unaffected):
almanah_0.11.1-1.dsc
bijiben_3.18.0-1.dsc
ekiga_4.0.1-6.dsc
eweouz_0.10.dsc
folks_0.11.1-2.dsc
glabels_3.0.1-4.1.dsc
gnome-calendar_3.16.2-1.dsc
gnome-contacts_3.18.0-1.dsc
gnome-panel_3.18.0-1.dsc
gnome-phone-manager_0.69-2.dsc
jana_0.0.0+git20091215.9ec1da8a-3.dsc
mail-notification_5.4.dfsg.1-14.dsc
roger-router_1.8.9-5.dsc
ls: cannot access sflphone_*.dsc: No such file or directory
syncevolution_1.4.99.4-4.dsc
ls: cannot access evolution-ews_*.dsc: No such file or directory
ls: cannot access evolution-ews_*.dsc: No such file or directory
ls: cannot access evolution-mapi_*.dsc: No such file or directory
ls: cannot access evolution-rss_*.dsc: No such file or directory
ls: cannot access evolution-webcal_*.dsc: No such file or directory
ls: cannot access evolution_*.dsc: No such file or directory
gnome-shell_3.16.3-2.dsc
abiword_3.0.1-4.dsc
sflphone failure seems unrelated to e-d-s, looks NMU-maintained and it
has no reverse dependencies.
I'd suggest handling with a temporary removal from testing for now.
evolution{,-ews,-mapi} needs sourceful uploads to latest upstream stable
release. I'll prepare these in experimental for now.
evolution-rss fails... It has no reverse dependencies.
I'd suggest handling with a temporary removal from testing for now.
evolution-webcal fails... I can't find upstream location. No reverse
dependencies.
I'd suggest handling with a temporary removal from testing for now.
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Bug#800599: transition: evolution-data-server 3.18
On Thu, Oct 01, 2015 at 04:29:31PM +0200, Andreas Henriksson wrote:
[...]
> evolution{,-ews,-mapi} needs sourceful uploads to latest upstream stable
> release. I'll prepare these in experimental for now.
[...]
These have now been uploaded to experimental.
Any remaining blockers for this transition?
Regards,
Andreas Henriksson
Bug#800599: transition: evolution-data-server 3.18
On Thu, Oct 01, 2015 at 08:14:50PM +0200, Emilio Pozuelo Monfort wrote: [...] > Please file a bug for sflphone. http://bugs.debian.org/800652 > > Also it'd be good to get the evolution-rss build error fixed. Though I'd be > happy enough if you report the failure upstream and ask for a new release :-) Not sure what the hickup was yesterday it now builds here. :) > > Otherwise, you're free to go. Thanks. If not today, will start uploading on monday Regards, Andreas Henriksson
Bug#800599: eds transition started, time for binNMUs
Hello!
The evolution{,-data-server,-ews,-mapi} packages has been uploaded
and built everywhere except mips* which is still playing catchup.
Please fire up binNMUs for remaining packages in the transition.
Regards,
Andreas Henriksson
Bug#800599: eds transition started, time for binNMUs
Hello Andreas Beckmann. On Wed, Oct 07, 2015 at 11:25:55PM +0200, Andreas Beckmann wrote: > Something does not look right, many packages (e.g. evolution-ews, > evolution-mapi, ...) pick up a > Depends: evolution (>= 3.16.3), evolution (<< 3.17) > which is not satisfiable in sid (which now has 3.18.0-2). > Rebuilding evolution-ews locally in an up-to-date sid did not fix this. Thanks for poking me about this fixed version uploaded now. Regards, Andreas Henriksson
Bug#594825: RM: henplus/0.9.7.ds1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Given the low popcon of henplus, the unusable status of it for over a year and a half, the lack of response from the maintainer, the availability of working unofficial packages, ... I'd like to request it's removal. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526898 http://qa.debian.org/popcon.php?package=henplus -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (300, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100829214001.ga6...@amd64.fatal.se
Bug#639871: transition: gssdp/gupnp
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition The GUPnP stack has been released in a new major upstream versions and the two base components (gssdp & gupnp) have bumped their sonames "now that we're breaking API/ABI"[1][2]. The new stack has been uploaded to experimental, with gssdp and gupnp currently stuck in NEW. I've compared the dpkg-gensymbols generated symbols files and no symbols are missing in the new library version. I see some changes related to improving the situation for bindings, so I guess some data structures might have changed that broke the ABI. I don't see any reasons why reverse dependencies should have any problems building against the new versions, but I've only tested a few random ones (like gupnp-igd, bickley, ...). One exception is rygel, which has (too) strict configure checks and will need a sourceful upload, but I'll handle that being the maintainer for it as well. [1] http://git.gnome.org/browse/gssdp/commit/?id=e937ef0b688b4764a4db7d23f8cd3ff7fb72affb [2] http://git.gnome.org/browse/gupnp/commit/?id=71a93a7b116ed0bef725a88cedc3bb1414cb1d5a -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (300, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110831080201.9066.73437.report...@amd64.fatal.se
Bug#639871: gupnp stack reverse build dependencies
for reference:
$ for pkg in lib{gssdp,gupnp,gupnp-av,gupnp-dlna}-1.0-dev ; do grep-dctrl
-sPackage -i -r -F Build-Depends,Build-Depends-Indep "\b$pkg\b"
/var/lib/apt/lists/*_Sources ; done | awk '{ print $2 }' | sort -u
amsn
bickley
bognor-regis
enna
grilo-plugins
gupnp
gupnp-av
gupnp-igd
gupnp-tools
gupnp-vala
nautilus-sendto
rygel
upnp-router-control
Of these gupnp, gupnp-av, gupnp-vala and rygel will get sourceful uploads.
The rest should hopefully just need a binNMU.
--
Andreas Henriksson
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111006154902.ga9...@amd64.fatal.se
#520646: binNMU oprofile
20:44 < fatal> please binNMU oprofile, see #520646. 20:44 < dato> fatal: please send mail -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Give back iproute on mipsel
Hello! Please trigger another attempt at building iproute on mipsel, which seems to yet again have failed because of linux-libc-dev < 2.6.29 being broken on mips*. The new linux-libc-dev 2.6.29-1 seems to be available on mipsel now so hopefully it'll work this time. Thanks in advance. PS. kicking whoever is responsible for mips to upload the already built iproute package would also be appreciated. -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
please binNMU libpam-p11 because of libp11
Hello. libpam-p11 seems to build fine with libp11-1, please binNMU libpam-p11 to get rid of the dependency on libp11-0 (which is not available anymore). -- Andreas Henriksson signature.asc Description: Digital signature
Suggestion for "fixing" RC bugs (binNMU + removal(s)).
* binNMU for libgnorba27 (src:gnome-libs) should fix: #472861: libgnorba27 is uninstallable * Removal for gnome-lokkit (and lokkit while at it) because of: #473278: gnome-lokkit: FTBFS as libgnome-dev is not installable in sid #395690: gnome-lokkit: missing binary-indep target in debian/rules (Policy 4.9) #460774: gnome-lokkit: your package depends from gnome-libs that is scheduled for removal -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Suggestion for "fixing" RC bugs (binNMU + removal(s)).
Hello Chris! Couldy you please state your opinion about removal of *lokkit from Debian, as you are listed as the maintainer? On sön, 2008-04-13 at 02:32 -0700, Steve Langasek wrote: [...] > > #395690: gnome-lokkit: missing binary-indep target in debian/rules > > (Policy 4.9) > > It looks like this bug should be raised to severity: serious, in which case > it would be grounds for removal from testing. > > > #460774: gnome-lokkit: your package depends from gnome-libs that is > > scheduled for removal > > But this looks to me like a reason to remove the package from unstable, not > from testing. > -- Regards, Andreas Henriksson
Please consider unblocking iproute 20080725-2
Hello Release Team! The iproute package in unstable unfortunately missed getting an automatic freeze exception. I'd like to ask you to please review it and consider unblocking it. The new upstream release mainly contains bugfixes, among others the fix for #488430: iproute: lnstat causes segmentation fault. Upstream changelog is available at: http://www.spinics.net/lists/netdev/msg70385.html It's been built on all (linux) achitectures and no new problems has been reported during it's time in unstable. Additionally the priority has been adjusted for the binary iproute package, and ftp-masters have fixed the priority overrides as well (see #487533). Thanks for considering. -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[EMAIL PROTECTED]: Mail delivery failed: returning message to sender]
Hello again. Host liszt.debian.org seems to have been broken for the past day or two. Now that it's up I instead got a permanent error. Lets try without the debdiff and see if we can get through - Forwarded message from Mail Delivery System <[EMAIL PROTECTED]> - Subject: Mail delivery failed: returning message to sender debian-release@lists.debian.org SMTP error from remote mail server after end of data: host liszt.debian.org [2001:41b8:0:1003:213:21ff:fe20:1426]: 550 5.7.1 34 javascript -- This is a copy of the message, -- Hello! Please unblock awstats 6.7.dfsg-5, which I just uploaded. It includes a simple patch from upstream to fix a XSS issue (rated important by the security team, but can't hurt to include it in Lenny). The relevant debian bug number is #495432. Here's the debdiff between -4 and -5: - End forwarded message - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: two removal suggestions awl and gem
On mån, 2008-09-01 at 21:06 +0200, Thomas Viehmann wrote: > > - gem: multiple RC bugs with NMU proposal without comment for more > than >two months, but also seems in bad shape from looking at the >non-RC bugs: a segfault unsanswered by the maintainer for >8 months, a new upstream version (that looks like a bugfix >release) wishlist without maintainer reaction from June. >I'm CCing NMUer to be or not to be Andreas if he has any >insights. Removal seems best from my point of view as well. Noone apparently cares enough about the package to even offer to test the fixes. -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#695152: t-p-u pre-approval lftp/4.3.6-1+deb7u1
On Mon, Dec 10, 2012 at 10:44:43PM +0100, Julien Cristau wrote: > On Tue, Dec 4, 2012 at 18:21:25 +0100, Ivo De Decker wrote: > > > diff -Nru lftp-4.3.6/debian/patches/lftp_sys-stdint-kfreebsd.patch > > lftp-4.3.6/debian/patches/lftp_sys-stdint-kfreebsd.patch > > --- lftp-4.3.6/debian/patches/lftp_sys-stdint-kfreebsd.patch > > 1970-01-01 01:00:00.0 +0100 > > +++ lftp-4.3.6/debian/patches/lftp_sys-stdint-kfreebsd.patch > > 2012-12-01 17:42:44.0 +0100 > > @@ -0,0 +1,18 @@ > > +Description: prevent sys/_stdint.h from redefining intptr_t et.al. > > +Author: Andreas Henriksson > > +Bug-Debian: http://bugs.debian.org/677861 > > +Forwarded: no > > + > > +--- lftp-4.3.6.orig/lib/stdint.in.h > > lftp-4.3.6/lib/stdint.in.h > > +@@ -75,6 +75,10 @@ > > + _@GUARD_PREFIX@_STDINT_H is defined. > > + The include_next requires a split double-inclusion guard. */ > > + # @INCLUDE_NEXT@ @NEXT_STDINT_H@ > > ++#ifdef __FreeBSD_kernel__ > > ++// prevent sys/_stdint.h from being included and redefine intptr_t et.al. > > ++#define _SYS__STDINT_H_ > > ++#endif > > + #endif > > + > > + #if ! defined _@GUARD_PREFIX@_STDINT_H && ! defined > > _GL_JUST_INCLUDE_SYSTEM_STDINT_H > > That is rather horrible. I probably don't want to know why this is > necessary. Reluctant ack, go ahead with the upload. Sorry for sharing some insight despite you not wanting to know ;P I fully agree with it being horrible, that's why I didn't want to upload it myself. On the other hand, since the maintainer acked Ivos NMU it's not my place to disagree either. A much better solution would have been to actually fix the kFreeBSD system headers! (The details are available in the original lftp bug report referenced in the patch headers.) Unfortunately noone seems interested in doing that. On the other hand, I guess it could also be considered a bug in portability layers like "gnulib" to not correctly handle the brokenness (even after kFreeBSD headers potentially gets fixed) so someone should work with upstream gnulib to find a suitable longterm- maintainable fix! (Completely blocking a system header isn't very nice. Even though that header today just contain redundant crap, that could potentially change in the future.) This patch is a from my point of view a double workaround. Work around kFreeBSD brokenness and work around the release teams need to punish all (Linux) users of lftp with a removal because of kFreeBSD brokenness. I would not want to carry a patch like this in a package I maintain. I hope noone will blame me later for this patch, because please remember that I did not upload it and take no responsability for it. -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121212153137.ga19...@amd64.fatal.se
Bug#689697: unblock: rygel/0.14.3-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package rygel Upstream recommended to include a trivial patch that improves the interopability with many DLNA devices on the market that always does seek requests. Without this patch these users won't get smooth playback. (ie. many BlueRay Disc players on the market apparently have this bug). http://git.gnome.org/browse/rygel/commit/?h=rygel-0-14&id=6afee764be64d0239d426f48cc7754aa6ad97ef9 unblock rygel/0.14.3-2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (300, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121005094100.14145.73990.report...@amd64.fatal.se
Bug#689698: unblock: gupnp/0.10.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock packages in the gupnp stack The upstream stable series bugfix updates has been sitting in unstable for over a month now without a single bug reported. The updates improves interopability with DLNA devices on the market and is for some users essential fixes. source packages to unblock: gssdp 0.12.2.1-1 gupnp 0.18.4-1 gupnp-av 0.10.3-1 gupnp-vala 0.10.4-1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (300, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121005093435.14027.76514.report...@amd64.fatal.se
Re: Pre-approval request for upload of iproute
Hello! On Wed, Oct 10, 2012 at 09:50:24PM +0200, Julien Cristau wrote: > On Mon, Aug 6, 2012 at 13:12:14 +0200, Andreas Henriksson wrote: > > > Hello! > > > > I'm seeking pre-approval for uploading the new upstream iproute2 > > release (20120801 a.k.a. v3.5.0, currently sitting in experimental) > > targeting wheezy (via unstable). > > > I see there's now an even newer version in experimental. Is that still > something you'd like in wheezy? I thought this issue was finalized after our last discussion on IRC. If 3.5 was too controversial back then, 3.6 is probably even more so today. I won't push for this inclusion in wheezy myself anymore, but I did consider it a waste to not give users the many small improvements that has been made later on. Also as indicated many will probably want CoDeL since it's part of the magic recepie for fixing bufferbloat (and since backporting BQL was approved, why not fully support this out of the box on wheezy with a matching iproute2 version?). Maybe someone will step up to do a wheezy-backport for those who needs it since iproute2 basically has no dependencies, it'll be trivial to make. If you're just asking for my recommendation on what to ship I'd currently suggest the version in experimental plus this patch: http://git.kernel.org/?p=linux/kernel/git/shemminger/iproute2.git;a=commitdiff;h=7f747fd9377b8538adeba7332d25905ba08ac156 (I'll look at getting this patch into experimental ASAP.) Having said that, shipping the version in wheezy is not in any way a disaster. (just a bit of a dissapointment.) Looking forward to getting the wheezy release shipped (no matter the state of iproute2)! Have a nice day! -- Andreas Henriksson signature.asc Description: Digital signature
Bug#689698: unblock: gupnp/0.10.3-1
Hello! On Sat, Oct 13, 2012 at 12:24:56PM +0100, Adam D. Barratt wrote: [...] > What's the rationale behind the debhelper compat bumps in gupnp-vala > and gssdp? They're not really great changes to be making during a > freeze unless there's some specific reason for it (and even then > there's often a more suitable way of solving the issue). First... updating gupnp-vala is not strictly needed. It doesn't really bring anything, just drops off stuff no longer needed. We can skip gupnp-vala if you prefer. Maybe I should have avoided bumping the dh compat for gssdp. On the other hand I knew it was compatible already and I'm very confident it's not going to cause any problems. My intention was that it was going to prepare for hardening the packages. IIRC I did not have a better reason for it than that + the rest of the gupnp stack was already at version 9. The change was sitting in pkg-vcs (git) for a long time so I was just to lazy to back it out (but it was a while ago so my memory is not 100% up to date). Please trust me that I will take full responsibility for any breakage and will be available to quickly fix issues if any should show up. -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121013153819.gb4...@amd64.fatal.se
Bug#689698: please unblock gupnp stack
Hello! About a month has passed since our last interaction, so maybe it's time for another reminder from me. Please unblock packages in the gupnp stack Not a single bug report has been filed, so there should be little worry that there is any problems caused by letting the updated packages into testing - while allowing the affected people to get compatibility fixes part of the new stable upstream releases. (I would also like to question the moreinfo tag put on the bug. Please tell me what info you think is needed.) -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121109121103.ga9...@amd64.fatal.se
Bug#689698: please unblock gupnp stack
On Sat, Dec 01, 2012 at 02:29:29PM +0100, Julien Cristau wrote: > The thing is, these updated packages mean rather big diffs, and don't > seem to close any reported bugs, according to the changelogs. So I'm > afraid this isn't a very high priority. If there is anything I can do from my end to make it easier for you, please tell me... Interopability is everything for this kind of software. If I don't hear anything I'll trust you know what's best for our users and simply leave the packages to their destiny. -- Andreas Henriksson signature.asc Description: Digital signature
Bug#768315: unblock: util-linux/2.25.2-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I'm seeking pre-approval for a not-yet-uploaded version of util-linux. Justification: probably better to revert and postpone to Jessie+1. Bug number/severity: #767194 important Changelog entry: Ship fstrim timer/service units as examples only Full description and debdiff below Please (eventually) unblock package util-linux Explanation of changes: Martin Pitt reported fstrim taking a long time on his system and in combination with init-system-helpers (dh_systemd) starting the fstrim /service/ in postinst this will make the package upgrade take a long time. An improvement to dh_systemd_start has been suggested in #767429. Apart from that, others have expressed that we're apparently not yet mentally ready for shipping systemd units in Debian. Lets just ship the unit files as examples for now and let people continue to trim their SSDs manually (or manually set up their preferred method of having it done regularly for them). Closes: #767194 === debdiff diff -Nru util-linux-2.25.2/debian/changelog util-linux-2.25.2/debian/changelog --- util-linux-2.25.2/debian/changelog 2014-10-24 18:57:51.0 +0200 +++ util-linux-2.25.2/debian/changelog 2014-11-06 13:54:11.0 +0100 @@ -1,3 +1,9 @@ +util-linux (2.25.2-3) unstable; urgency=medium + + * Ship fstrim timer/service units as examples only (Closes: #767194) + + -- Andreas Henriksson Thu, 06 Nov 2014 13:54:04 +0100 + util-linux (2.25.2-2) unstable; urgency=medium * Only ship fstrim service and timer on linux diff -Nru util-linux-2.25.2/debian/util-linux.install util-linux-2.25.2/debian/util-linux.install --- util-linux-2.25.2/debian/util-linux.install 2014-10-24 18:57:51.0 +0200 +++ util-linux-2.25.2/debian/util-linux.install 2014-11-06 13:54:11.0 +0100 @@ -10,8 +10,8 @@ [linux-any] sbin/mkswap [!linux-any] debian/tmp/sbin/mkswap => /sbin/mkswap.linux # weekly fstrim only available on linux -[linux-any] lib/systemd/system/fstrim.timer -[linux-any] lib/systemd/system/fstrim.service +[linux-any] lib/systemd/system/fstrim.timer => /usr/share/doc/util-linux/examples/fstrim.timer +[linux-any] lib/systemd/system/fstrim.service => /usr/share/doc/util-linux/examples/fstrim.service bin/more sbin/agetty sbin/blkid diff -Nru util-linux-2.25.2/debian/util-linux.preinst util-linux-2.25.2/debian/util-linux.preinst --- util-linux-2.25.2/debian/util-linux.preinst 1970-01-01 01:00:00.0 +0100 +++ util-linux-2.25.2/debian/util-linux.preinst 2014-11-06 13:54:11.0 +0100 @@ -0,0 +1,13 @@ +#!/bin/sh +set -e + +# We once shipped fstrim.timer in 2.25.2-2. Undo the timer getting enabled +# and purge the helper state, if upgrading from that version. +if [ "$1" = "upgrade" ] && [ "$2" = "2.25.2-2" ] && \ + [ -x /usr/bin/deb-systemd-helper ] && \ + deb-systemd-helper debian-installed fstrim.timer; then + deb-systemd-helper disable fstrim.timer + deb-systemd-helper purge fstrim.timer +fi + +#DEBHELPER# unblock util-linux/2.25.2-3 -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141106130351.26654.64629.report...@mbpah.endian.se
Bug#768315: unblock: util-linux/2.25.2-3
On Thu, Nov 06, 2014 at 05:09:43PM +0100, Julien Cristau wrote: > Why not do that in postinst when you know deb-systemd-helper is > available? You mean switch from preinst upgrade to postinst configure... sure could do that. On the other hand, if we're upgrading from the given version then we already have everything needed in place so shouldn't matter either way, right? ie. this only affects up to date testing/sid. Noone else. Want me to post a new patch that does postinst configure instead? Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141106170921.ga3...@fatal.se
Bug#768315: unblock: util-linux/2.25.2-3
On Thu, Nov 06, 2014 at 05:26:04PM +, Gerrit Pape wrote: > Hi, installing the unit files, which AFAICS entered jessie quite > recently, also introduced a dependency on init-system-helpers and in > turn on perl, making perl pseudo-essential (#757891). Can we revert > this too? This dependency automatically dissapears with the proposed change. (For the future you should not be holding your breath that I will be sentimental about reintroducing it though. A solution on the perl side is needed.) Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141106185536.ga3...@fatal.se
Re: Bug#769273: bsdutils: Dependency on libsystemd0 violates policy
Hello Tim Wootton, release-team, et.al.! Thanks for your bug report. On Wed, Nov 12, 2014 at 11:00:16AM +, Tim Wootton wrote: > Package: bsdutils > Version: 1:2.25.2-2 > Severity: serious > Justification: Policy 2.5 > > Dear Maintainer, > > libsystemd0 dependancy violates constraint at the end of section 2.5 > of the policy manual that requires packages not depend on packages > with lower priority. This (general) problem has been discussed (several times?) on debian-devel already and as far as I remember and understood it was that raising the priority of the relevant systemd binary packages could be done but it did not solve any *practical* problem. Instead it seemed easier to just fix policy. I guess that's where everyone lost interest I'd like to defer this issue to release team to decide what the best course of action is. They can decide if this is a wontfix/jessie-ignore, if policy editors must update the policy before the jessie release or if systemd maintainers needs to adjust their priority. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141112140456.ga18...@fatal.se
Bug#768315: unblock: util-linux/2.25.2-3
Hello intrigeri! On Sat, Nov 15, 2014 at 12:51:53PM +0100, intrigeri wrote: > Hi Andreas, > > Agreed. I think we should ship the cronjob by default in Jessie. > Andreas, what do you think? What I've seen so far is people suggesting to use a cron job /instead of/ the systemd units shipped by upstream. That is in my opinion pretty short-sighted. I see a cron job as a complement that caters to the niche which does not use the default init in Jessie. Saying that people who don't install cron don't get their SSDs trimmed is just stupid. Speciall since installing cron also pulls in a full MTA. Why would anyone want to connect having an MTA installed to having their SSD trimmed?! Atleast I'm not going to install that on a number of my systems. (Please keep in mind that it's not uncommon even for embedded system to ship with SATA or mSATA today and those are being used with SSD drives.) I've spent way to much time catering to niches that random people think are important but where they don't want to do the work themselves. I'm not going to do that anymore, unless people agree to paying my regular fee for buying hours of my life which is the way I'm making a living.. (fwiw, I'm also still pondering if I still want to be involved with Debian at all.) If someone wants to do the work it would be good if they could think about the consequenses themselves, but here are some pro bono advice: There will likely be a number of people having both systemd and cron installed on their systems. Whoever does the work on the cron side will probably want to make sure that these people don't end up with double trimming. Also see: https://git.kernel.org/cgit/utils/util-linux/util-linux.git/tree/Documentation/howto-contribute.txt I really don't understand why we're having this discussion now at all. Where where everyone before the freeze? Where where the advice when I asked for it and had to fight my way forward to get my changes into Debian. Right now I'm really regretting even getting involved with util-linux in Debian. I should have just kept on doing my own thing and never mentioned it to anyone. I've spent a huge amount of time cleaning up the mess left by others and catered to all kinds of niches that didn't want to do their work themselves (most time occupied by kfreebsd). This left me with alot of people thinking because I did that now I somehow owe them even more time and work which they can dictate how I should do. I guess I'm drifting way off topic here trying to focus again. If you don't want to pay me to do the work, then get pre-approval from the release team for your suggested changes - then, and not before then, feel free to talk to me about it. I'm not interested before that. Things that will interest people who actually want to work on a solution for keeping automatic trimming: 1/ #757891 see also: https://lists.debian.org/debian-devel/2014/11/msg00216.html 2/ #767429 3/ optionally create a proper cron-job. 4/ get r-t pre-approval. Right now I see a number of flawed suggestions floating around. It's probably less interesting that I can't really approve of any of them, then that it will probably be hard to get any of it past the release team now. My suggestion is thus still that I'm not seeing the above points not getting fixed I think the safest way is to just back out all trimming jobs and make another attempt after the ice-age has passed. (If 1 and 2 gets fixed in Jessie, then I'll close my pre-approval request to drop the units from the current util-linux package. If someone can also get 3 and 4 done, then good for the people who benefit from that!) HTH. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141115215750.ga25...@fatal.se
Bug#768315: uploaded, please unblock.
Hello! As discussed on IRC, I've uploaded 2.25.2-3 to work around the issues that surfaced with the introduction of a timer unit. Please unblock. People might want to clone this bug report and continue their discussions on cron jobs in the clone. Please leave me out of that discussion! Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141117104430.ga8...@fatal.se
Bug#770204: unblock: gnome-logs/3.14.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hello! The gnome-logs package unfortunately ships broken files which makes it not possible to start from a GUI. (See http://bugs.debian.org/770148 ) I'd like to ask for pre-approval of the following filtered debdiff which was prepared using: debdiff /var/cache/pbuilder/result/gnome-logs_3.14.[12]-1*.dsc | filterdiff -x '*/po/*' -x '*/ChangeLog' -x '*/configure' -x '*/Makefile.in' ie. excluding translations and autogenerated files. = diff -Nru gnome-logs-3.14.1/ChangeLog gnome-logs-3.14.2/ChangeLog diff -Nru gnome-logs-3.14.1/configure gnome-logs-3.14.2/configure diff -Nru gnome-logs-3.14.1/configure.ac gnome-logs-3.14.2/configure.ac --- gnome-logs-3.14.1/configure.ac 2014-10-13 21:20:25.0 +0200 +++ gnome-logs-3.14.2/configure.ac 2014-11-10 23:00:40.0 +0100 @@ -1,5 +1,5 @@ AC_INIT([Logs], -[3.14.1], +[3.14.2], [dav...@gnome.org], [gnome-logs], [https://wiki.gnome.org/Apps/Logs]) @@ -15,6 +15,7 @@ dnl Check for programs AC_PROG_CC AM_PROG_CC_C_O +AC_PROG_SED GNOME_COMPILE_WARNINGS([maximum]) @@ -93,7 +94,6 @@ PKG_CHECK_MODULES([LOGS], [$GIO_REQUIRED $GTK_REQUIRED $SYSTEMD_JOURNAL_REQUIRED]) AC_CONFIG_FILES([ -data/org.gnome.Logs.service data/version.xml help/Makefile Makefile diff -Nru gnome-logs-3.14.1/data/org.gnome.Logs.appdata.xml.in gnome-logs-3.14.2/data/org.gnome.Logs.appdata.xml.in --- gnome-logs-3.14.1/data/org.gnome.Logs.appdata.xml.in2014-08-18 13:36:08.0 +0200 +++ gnome-logs-3.14.2/data/org.gnome.Logs.appdata.xml.in2014-10-28 08:43:43.0 +0100 @@ -4,10 +4,9 @@ org.gnome.Logs.desktop CC0-1.0 GPL-3.0+ - + +<_name>Logs +<_summary>View detailed event logs for the system <_p>Logs shows events from the systemd journal, and sorts them into categories, such as hardware and applications. diff -Nru gnome-logs-3.14.1/debian/changelog gnome-logs-3.14.2/debian/changelog --- gnome-logs-3.14.1/debian/changelog 2014-10-19 23:09:59.0 +0200 +++ gnome-logs-3.14.2/debian/changelog 2014-11-19 15:45:37.0 +0100 @@ -1,3 +1,10 @@ +gnome-logs (3.14.2-1) unstable; urgency=medium + + * New upstream release +- fixes desktop file generation (Closes: #770148) + + -- Andreas Henriksson Wed, 19 Nov 2014 15:45:34 +0100 + gnome-logs (3.14.1-1) unstable; urgency=medium * New upstream release. diff -Nru gnome-logs-3.14.1/help/Makefile.in gnome-logs-3.14.2/help/Makefile.in diff -Nru gnome-logs-3.14.1/Makefile.am gnome-logs-3.14.2/Makefile.am --- gnome-logs-3.14.1/Makefile.am 2014-09-12 17:32:12.0 +0200 +++ gnome-logs-3.14.2/Makefile.am 2014-11-10 23:00:20.0 +0100 @@ -80,8 +80,12 @@ $(desktop_in_files:.desktop.in=.desktop): data/.dstamp desktop_DATA = $(desktop_in_files:.desktop.in=.desktop) +data/org.gnome.Logs.service: data/org.gnome.Logs.service.in + $(AM_V_GEN)$(SED) -e "s|[@]bindir[@]|$(bindir)|" $< > $@ + servicedir = $(datadir)/dbus-1/services -service_DATA = data/org.gnome.Logs.service +service_in_files = data/org.gnome.Logs.service.in +service_DATA = $(service_in_files:.service.in=.service) if ENABLE_MAN data/gnome-logs.1: data/gnome-logs.xml @@ -172,6 +176,7 @@ $(noinst_resource_files) \ $(appstream_in_files) \ $(desktop_in_files) \ + $(service_in_files) \ data/org.gnome.Logs.gresource.xml \ data/gnome-logs.xml \ data/icons/gnome-logs.svg @@ -198,6 +203,7 @@ $(desktop_DATA) \ $(enum_data) \ $(nodist_man_MANS) \ + $(service_DATA) \ src/gl-resource.c \ src/gl-resource.h \ test-desktop-file-validate.sh diff -Nru gnome-logs-3.14.1/Makefile.in gnome-logs-3.14.2/Makefile.in diff -Nru gnome-logs-3.14.1/NEWS gnome-logs-3.14.2/NEWS --- gnome-logs-3.14.1/NEWS 2014-10-13 21:21:28.0 +0200 +++ gnome-logs-3.14.2/NEWS 2014-11-10 23:02:05.0 +0100 @@ -1,3 +1,10 @@ +GNOME Logs 3.14.2 += + +* substitute binary path in service file correctly +* add elements to AppData to fix validation +* Thai translation + GNOME Logs 3.14.1 = diff -Nru gnome-logs-3.14.1/po/kk.po gnome-logs-3.14.2/po/kk.po diff -Nru gnome-logs-3.14.1/po/LINGUAS gnome-logs-3.14.2/po/LINGUAS diff -Nru gnome-logs-3.14.1/po/th.po gnome-logs-3.14.2/po/th.po diff -Nru gnome-logs-3.14.1/src/gl-eventviewlist.c gnome-logs-3.14.2/src/gl-eventviewlist.c --- gnome-logs-3.14.1/src/gl-eventviewlist.c2014-07-21 21:21:36.0 +0200 +++ gnome-logs-3.14.2/src/gl-eventviewlist.c2014-11-10 23:00:20.0 +0100 @@ -924,6 +924,7 @@ break; case PROP_MODE:
Bug#770204: unblock: gnome-logs/3.14.2-1
Hello Niels Thykier. On Wed, Nov 19, 2014 at 08:08:31PM +0100, Niels Thykier wrote: > Ack, please upload this and let us know when it has been accepted into > unstable. Thanks. Uploaded now! Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2014112402.ga9...@fatal.se
Bug#770338: unblock: nautilus/3.14.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hello! I'd like to ask for another pre-approval. This time it's fixing a regression when tweaking so that nautilus handles the desktop. Many people seem to still want to have icons on the (gnome-shell) desktop and are now running into #766021 (and duplicates). Additional minor bugfixes included as a bonus. I'm attaching a filtered debdiff, created by using: debdiff /var/cache/pbuilder/result/nautilus_3.14.[01]-1*dsc | filterdiff -x '*/Makefile.in' -x '*/aclocal.m4' -x '*/configure' -x '*/docs/*' -x '*/po/*' -x '*/data/*.in' -x '*/data/*.desktop' ie. excluding autogenerated files and translations. === diff -Nru nautilus-3.14.0/aclocal.m4 nautilus-3.14.1/aclocal.m4 diff -Nru nautilus-3.14.0/configure nautilus-3.14.1/configure diff -Nru nautilus-3.14.0/configure.ac nautilus-3.14.1/configure.ac --- nautilus-3.14.0/configure.ac2014-09-23 12:16:06.0 +0200 +++ nautilus-3.14.1/configure.ac2014-11-12 23:53:46.0 +0100 @@ -18,7 +18,7 @@ m4_define(nautilus_extension_current, 5) m4_define(nautilus_extension_revision, 0) -AC_INIT([nautilus],[3.14.0],[http://bugzilla.gnome.org/enter_bug.cgi?product=nautilus]) +AC_INIT([nautilus],[3.14.1],[http://bugzilla.gnome.org/enter_bug.cgi?product=nautilus]) dnl === diff -Nru nautilus-3.14.0/data/nautilus-autorun-software.desktop.in nautilus-3.14.1/data/nautilus-autorun-software.desktop.in diff -Nru nautilus-3.14.0/data/nautilus-connect-server.desktop.in nautilus-3.14.1/data/nautilus-connect-server.desktop.in diff -Nru nautilus-3.14.0/data/org.gnome.Nautilus.desktop nautilus-3.14.1/data/org.gnome.Nautilus.desktop diff -Nru nautilus-3.14.0/data/org.gnome.Nautilus.desktop.in nautilus-3.14.1/data/org.gnome.Nautilus.desktop.in diff -Nru nautilus-3.14.0/debian/changelog nautilus-3.14.1/debian/changelog --- nautilus-3.14.0/debian/changelog2014-09-23 15:50:26.0 +0200 +++ nautilus-3.14.1/debian/changelog2014-11-20 14:15:55.0 +0100 @@ -1,3 +1,10 @@ +nautilus (3.14.1-1) unstable; urgency=medium + + * New upstream release. +- includes fix for --new-window (Closes: #766021) + + -- Andreas Henriksson Thu, 20 Nov 2014 14:15:54 +0100 + nautilus (3.14.0-1) unstable; urgency=medium * New upstream release. diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-column.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-column.html diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-column-provider.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-column-provider.html diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-extension-types.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-extension-types.html diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-file-info.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-file-info.html diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-info-provider.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-info-provider.html diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-location-widget-provider.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-location-widget-provider.html diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-menu.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-menu.html diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-menu-provider.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-menu-provider.html diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-property-page.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-property-page.html diff -Nru nautilus-3.14.0/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-property-page-provider.html nautilus-3.14.1/docs/reference/libnautilus-extension/html/libnautilus-extension-nautilus-property-page-provider.html diff -Nru nautilus-3.14.0/libnautilus-private/nautilus-file-operations.c nautilus-3.14.1/libnautilus-pri
Bug#770338: unblock: nautilus/3.14.1-1
On Thu, Nov 20, 2014 at 07:58:20PM +, Jonathan Wiltshire wrote: > Please go ahead, and ping this bug when uploaded. Thanks. Uploaded. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141120212330.ga23...@fatal.se
Bug#769295: Bug#769290: libarchive: Zip file extract produces zero size files
¡Hola Maximiliano, release-team! Sorry for the delay! New libarchive with the proposed upstream commit cherry-picked into debian/patches uploaded. Thanks for your help. Release-team, please note the version number: 3.1.2-10 unblock libarchive/3.1.2-10 (The initial unblock bug report stated wrong version.) Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141120213151.ga23...@fatal.se
Bug#770414: unblock: gtk+3.0/3.14.5-1
Hello! On Fri, Nov 21, 2014 at 05:51:36AM +, Adam D. Barratt wrote: > Control: tags -1 + moreinfo [...] > That would need someone to provide the information requested in > https://release.debian.org/jessie/freeze_policy.html#getting-unblocks Matt is aware of this information already. Hopefully he'll follow up with additional information as requested soon. I'd expect that a filtered diff would be appreciated so the release-team don't have to look at for example the changes only relevant for Windows and OS X. > > Personally, I'd also like some input from the maintainers, as it's not > at all clear to me whether they were intending to try and get that > version in to jessie. I can't speak for pochus intentions with the upload, but he should be well aware of our freeze situation which probably meant he intended it to go into Jessie. I don't see any reason not to include it in Jessie so ACK from me. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141121120813.ga25...@fatal.se
Bug#770414: unblock: gtk+3.0/3.14.5-1
Hello again! Heavily filtered debdiff included debdiff *.dsc | filterdiff -x '*/build/win32/*' -x '*/*/*.po' -x '*/gdk/quartz/*' -x '*/docs/*' -x '*/INSTALL' -x '*/README' -x '*/build/*msvc*' -x '*/*win32' -x '*/gdk/win32/rc/gdk.rc' -x '*/configure' -x '*/*/*.pot' -x '*/gdk/broadway/*.h' -x '*/gtk/gtkresources.c' -x '*/gtk/resources/*' -x '*/gtk/gtkversion.h' -x '*/gdk/gdkversionmacros.h' -x '*/debian/control' -x '*/debian/patches/*' -x '*/gtk/gtkmenu.c' Summary of what was filtered out: - ms windows related changes - quartz (osx) related changes - built/autogenerated noise (eg. version number bump related, etc.) - css fixes in default adwaita theme - changes for previously shipped debian/patch now merged upstream. - translations Not sure this complies with release-team normal procedures but for a proper review I'd suggest looking at each commit in the upstream repository separately together with the explanation in the commit message and the referenced bug. See 3.14.4 -> 3.14.5 at: https://git.gnome.org/browse/gtk+/log/?h=gtk-3-14 I guess the result is still a bit to big for the release-teams taste, but when looking at each fix individually I'm can't really spot one that I'd say we could/should exclude. They're all nice to have and they do benefit alot of users, while being as small as possible. If in doubt I'd suggest to leave it in unstable for a week or two more just to let it get some more testing and chance for people to report bugs against it if they can find any, then look at it again to see if it's time to unblock. If you still disagree, then I think Matt would welcome some hints on how he can go about getting a targeted fix in for the particular problem he cares about diff -Nru gtk+3.0-3.14.4/build/gtk-introspection-msvc.mak gtk+3.0-3.14.5/build/gtk-introspection-msvc.mak diff -Nru gtk+3.0-3.14.4/build/win32/vs10/broadwayd.vcxproj gtk+3.0-3.14.5/build/win32/vs10/broadwayd.vcxproj diff -Nru gtk+3.0-3.14.4/build/win32/vs10/broadwayd.vcxproj.filters gtk+3.0-3.14.5/build/win32/vs10/broadwayd.vcxproj.filters diff -Nru gtk+3.0-3.14.4/build/win32/vs10/gtk-copy-gdk-broadway.props gtk+3.0-3.14.5/build/win32/vs10/gtk-copy-gdk-broadway.props diff -Nru gtk+3.0-3.14.4/build/win32/vs10/gtk-install.props gtk+3.0-3.14.5/build/win32/vs10/gtk-install.props diff -Nru gtk+3.0-3.14.4/build/win32/vs10/gtk-version-paths.props gtk+3.0-3.14.5/build/win32/vs10/gtk-version-paths.props diff -Nru gtk+3.0-3.14.4/build/win32/vs11/broadwayd.vcxproj gtk+3.0-3.14.5/build/win32/vs11/broadwayd.vcxproj diff -Nru gtk+3.0-3.14.4/build/win32/vs11/broadwayd.vcxproj.filters gtk+3.0-3.14.5/build/win32/vs11/broadwayd.vcxproj.filters diff -Nru gtk+3.0-3.14.4/build/win32/vs11/gtk-copy-gdk-broadway.props gtk+3.0-3.14.5/build/win32/vs11/gtk-copy-gdk-broadway.props diff -Nru gtk+3.0-3.14.4/build/win32/vs11/gtk-install.props gtk+3.0-3.14.5/build/win32/vs11/gtk-install.props diff -Nru gtk+3.0-3.14.4/build/win32/vs11/gtk-version-paths.props gtk+3.0-3.14.5/build/win32/vs11/gtk-version-paths.props diff -Nru gtk+3.0-3.14.4/build/win32/vs12/broadwayd.vcxproj gtk+3.0-3.14.5/build/win32/vs12/broadwayd.vcxproj diff -Nru gtk+3.0-3.14.4/build/win32/vs12/broadwayd.vcxproj.filters gtk+3.0-3.14.5/build/win32/vs12/broadwayd.vcxproj.filters diff -Nru gtk+3.0-3.14.4/build/win32/vs12/gtk-copy-gdk-broadway.props gtk+3.0-3.14.5/build/win32/vs12/gtk-copy-gdk-broadway.props diff -Nru gtk+3.0-3.14.4/build/win32/vs12/gtk-install.props gtk+3.0-3.14.5/build/win32/vs12/gtk-install.props diff -Nru gtk+3.0-3.14.4/build/win32/vs12/gtk-version-paths.props gtk+3.0-3.14.5/build/win32/vs12/gtk-version-paths.props diff -Nru gtk+3.0-3.14.4/build/win32/vs9/broadwayd.vcproj gtk+3.0-3.14.5/build/win32/vs9/broadwayd.vcproj diff -Nru gtk+3.0-3.14.4/build/win32/vs9/gtk-install.vsprops gtk+3.0-3.14.5/build/win32/vs9/gtk-install.vsprops diff -Nru gtk+3.0-3.14.4/build/win32/vs9/gtk-version-paths.vsprops gtk+3.0-3.14.5/build/win32/vs9/gtk-version-paths.vsprops diff -Nru gtk+3.0-3.14.4/config.h.win32 gtk+3.0-3.14.5/config.h.win32 diff -Nru gtk+3.0-3.14.4/configure gtk+3.0-3.14.5/configure diff -Nru gtk+3.0-3.14.4/configure.ac gtk+3.0-3.14.5/configure.ac --- gtk+3.0-3.14.4/configure.ac 2014-10-21 17:02:10.0 +0200 +++ gtk+3.0-3.14.5/configure.ac 2014-11-09 22:17:45.0 +0100 @@ -10,8 +10,8 @@ m4_define([gtk_major_version], [3]) m4_define([gtk_minor_version], [14]) -m4_define([gtk_micro_version], [4]) -m4_define([gtk_interface_age], [4]) +m4_define([gtk_micro_version], [5]) +m4_define([gtk_interface_age], [5]) m4_define([gtk_binary_age], [m4_eval(100 * gtk_minor_version + gtk_micro_version)]) m4_define([gtk_version], diff -Nru gtk+3.0-3.14.4/debian/changelog gtk+3.0-3.14.5/debian/changelog --- gtk+3.0-3.14.4/debian/changelog 2014-11-04 15:20:06.0 +0100 +++ gtk+3.0-3.14.5/debian/changelog 2014-11-11 18:55:48.0 +0100 @@ -1,3 +1,11 @@ +gtk+3.0 (3.14.5-1) unstable; urgency=medium + + * New upstream
Bug#684507: unblock: rygel/0.14.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package rygel It contains an important fix (workaround for gstreamer bug apparently) to avoid initial indexing of media taking really long time. This fix was recommended by upstreams Jens Georg (thanks) to include in Debian. (The new upstream release also contains another fix which we are already shipping as a patch, plus two translations Hopefully you agree that the changes are uncontroversal. Diff could be smaller if I continued patching, but I prefer shipping a proper release. I went ahead and uploaded it when I noticed that my Pre-approval request somehow had not reached the debian-release list.) Fwiw, please don't waste too much time reviewing the pre-generated C changes shipped in the upstream tarball since we rebuild everything with our own valac during package build anyway... unblock rygel/0.14.3-1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (300, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120810143744.1530.88382.report...@amd64.fatal.se
Bug#776989: unblock: util-linux/2.25.2-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package util-linux
The new revision of the package fixes a typo in the 2.25.2-4.1 NMU
(currently in testing) as well as works around problems in
live-tools and prevents partial upgrades vs grml-debootstrap.
Please note that the initramfs-tools version pulling in
parts of hwclock into the initramfs never made it into jessie.
Hopefully we can improve the situation so that it's not necessary
again during the Stretch development timeframe.
See attached git diff debian/2.25.2-4.1..debian/2.25.2-5
unblock util-linux/2.25.2-5
Thanks to both NMUers and all bug reporters for their interest
in improving the package.
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (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_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/changelog b/debian/changelog
index be2bc1b..7850238 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,24 @@
+util-linux (2.25.2-5) unstable; urgency=medium
+
+ * Revert "Trigger update of initramfs on upgrades" (Closes: #773354)
+ * Revert "Add Breaks: live-tools (<<4.0~alpha17-1)"
+- No longer needed since dropping the update-initramfs call.
+ * Fix typo in symlink_to_dir and bump prior-version
+- in other words, fix 2.25.2-4.1 upload. (Closes: #775350)
+ * Add Breaks: grml-debootstrap (<< 0.68)
+- previous versions does not work properly with new util-linux which
+ always identifies atleast one label for every partition (PARTUUID)
+ so lets prevent partial upgrades. (Closes: #772846)
+
+ -- Andreas Henriksson Tue, 03 Feb 2015 20:55:38 +0100
+
+util-linux (2.25.2-4.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add Breaks: live-tools (<<4.0~alpha17-1) (Closes: #773354)
+
+ -- Gaudenz Steinlin Sun, 01 Feb 2015 13:16:26 +0100
+
util-linux (2.25.2-4.1) unstable; urgency=medium
* Non-maintainer upload.
diff --git a/debian/control b/debian/control
index b829251..c92a833 100644
--- a/debian/control
+++ b/debian/control
@@ -38,7 +38,7 @@ Pre-Depends: ${misc:Pre-Depends}, ${shlibs:Depends}
Depends: initscripts, lsb-base (>= 3.0-6), tzdata (>=2006c-2), ${misc:Depends}
Suggests: dosfstools, kbd | console-tools, util-linux-locales
Replaces: bash-completion (<< 1:2.1-3)
-Breaks: bash-completion (<< 1:2.1-3)
+Breaks: bash-completion (<< 1:2.1-3), grml-debootstrap (<< 0.68)
Multi-Arch: foreign
Description: Miscellaneous system utilities
This package contains a number of important utilities, most of which
diff --git a/debian/libblkid-dev.maintscript b/debian/libblkid-dev.maintscript
index 3512d75..c43ec7d 100644
--- a/debian/libblkid-dev.maintscript
+++ b/debian/libblkid-dev.maintscript
@@ -1 +1 @@
-symlink_to_dir /usr/share/doc/libblkid-dev /usr/share/doc/libblkid 2.25.2-4
+symlink_to_dir /usr/share/doc/libblkid-dev /usr/share/doc/libblkid1 2.25.2-5~
diff --git a/debian/util-linux.postinst b/debian/util-linux.postinst
index 222491d..e9f2a69 100644
--- a/debian/util-linux.postinst
+++ b/debian/util-linux.postinst
@@ -21,10 +21,4 @@ if [ -L /usr/doc/util-linux ]; then
rm -f /usr/doc/util-linux
fi
-# (hwclock-related) parts of this package are being pulled into initramfs,
-# so trigger an update of the initramfs.
-if [ -x /usr/sbin/update-initramfs ]; then
- /usr/sbin/update-initramfs -u
-fi
-
#DEBHELPER#
Bug#777163: unblock: gnome-control-center/1:3.14.2-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gnome-control-center The new package revision reverts the changes in previous package revision to fix #774257. Having system-config-printer installed is still needed to be able to add new printers. For the details please see: https://git.gnome.org/browse/gnome-control-center/tree/panels/printers/pp-new-printer.c?h=gnome-3-14#n643 unblock gnome-control-center/1:3.14.2-3 -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (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_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Index: debian/changelog === --- debian/changelog (revision 44087) +++ debian/changelog (working copy) @@ -1,3 +1,10 @@ +gnome-control-center (1:3.14.2-3) unstable; urgency=medium + + * Re-add system-config-printer recommendation. (Closes: #774257) +- it's still needed to be able to add new printers. + + -- Andreas Henriksson Thu, 05 Feb 2015 19:44:41 +0100 + gnome-control-center (1:3.14.2-2) unstable; urgency=medium * Remove system-config-printer recommendation. Index: debian/control === --- debian/control (revision 44087) +++ debian/control (working copy) @@ -90,6 +90,7 @@ mousetweaks, policykit-1-gnome, rygel | rygel-tracker, +system-config-printer (>= 1.4), network-manager-gnome (>= 0.9.8), libnss-myhostname, cracklib-runtime, Index: debian/control.in === --- debian/control.in (revision 44087) +++ debian/control.in (working copy) @@ -86,6 +86,7 @@ mousetweaks, policykit-1-gnome, rygel | rygel-tracker, +system-config-printer (>= 1.4), network-manager-gnome (>= 0.9.8), libnss-myhostname, cracklib-runtime,
Bug#779846: unblock: libarchive/3.1.2-11
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libarchive A security issue was reported and an upstream commit has been cherry-picked to adress this issue. (Please note that this "vulnerability" is considered a feature in other implementations/systems, but oh well uploaded anyway.) See http://bugs.debian.org/778266 Thanks to contributors to that bug report. See attached diff for changes included... unblock libarchive/3.1.2-11 -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (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_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff --git a/debian/changelog b/debian/changelog index 7b5c1ff..2f53cae 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +libarchive (3.1.2-11) unstable; urgency=medium + + * Add d/p/Add-ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS-option.patch +(Closes: #778266) + + -- Andreas Henriksson Thu, 05 Mar 2015 14:54:43 +0100 + libarchive (3.1.2-10) unstable; urgency=medium * Add d/p/Do-not-overwrite-file-size-if-the-local-file-header-.patch diff --git a/debian/patches/Add-ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS-option.patch b/debian/patches/Add-ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS-option.patch new file mode 100644 index 000..08512dc --- /dev/null +++ b/debian/patches/Add-ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS-option.patch @@ -0,0 +1,142 @@ +From: Alessandro Ghedini +Date: Sun, 1 Mar 2015 12:07:45 +0100 +Subject: Add ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS option + +This fixes a directory traversal in the cpio tool. +--- + cpio/bsdcpio.1 | 3 ++- + cpio/cpio.c | 2 ++ + libarchive/archive.h | 2 ++ + libarchive/archive_write_disk.3 | 3 +++ + libarchive/archive_write_disk_posix.c| 14 +++--- + libarchive/test/test_write_disk_secure.c | 23 +++ + 6 files changed, 43 insertions(+), 4 deletions(-) + +diff --git a/cpio/bsdcpio.1 b/cpio/bsdcpio.1 +index b3d0d40..7794b0a 100644 +--- a/cpio/bsdcpio.1 b/cpio/bsdcpio.1 +@@ -156,7 +156,8 @@ See above for description. + .It Fl Fl insecure + (i and p mode only) + Disable security checks during extraction or copying. +-This allows extraction via symbolic links and path names containing ++This allows extraction via symbolic links, absolute paths, ++and path names containing + .Sq .. + in the name. + .It Fl J , Fl Fl xz +diff --git a/cpio/cpio.c b/cpio/cpio.c +index 6f57d95..f086203 100644 +--- a/cpio/cpio.c b/cpio/cpio.c +@@ -179,6 +179,7 @@ main(int argc, char *argv[]) + cpio->extract_flags |= ARCHIVE_EXTRACT_NO_OVERWRITE_NEWER; + cpio->extract_flags |= ARCHIVE_EXTRACT_SECURE_SYMLINKS; + cpio->extract_flags |= ARCHIVE_EXTRACT_SECURE_NODOTDOT; ++ cpio->extract_flags |= ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS; + cpio->extract_flags |= ARCHIVE_EXTRACT_PERM; + cpio->extract_flags |= ARCHIVE_EXTRACT_FFLAGS; + cpio->extract_flags |= ARCHIVE_EXTRACT_ACL; +@@ -264,6 +265,7 @@ main(int argc, char *argv[]) + case OPTION_INSECURE: + cpio->extract_flags &= ~ARCHIVE_EXTRACT_SECURE_SYMLINKS; + cpio->extract_flags &= ~ARCHIVE_EXTRACT_SECURE_NODOTDOT; ++ cpio->extract_flags &= ~ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS; + break; + case 'L': /* GNU cpio */ + cpio->option_follow_links = 1; +diff --git a/libarchive/archive.h b/libarchive/archive.h +index f56bc38..4e0b048 100644 +--- a/libarchive/archive.h b/libarchive/archive.h +@@ -562,6 +562,8 @@ __LA_DECL int archive_read_set_options(struct archive *_a, + /* Default: Do not use HFS+ compression if it was not compressed. */ + /* This has no effect except on Mac OS v10.6 or later. */ + #define ARCHIVE_EXTRACT_HFS_COMPRESSION_FORCED (0x8000) ++/* Default: Do not reject entries with absolute paths */ ++#define ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS (0x1) + + __LA_DECL int archive_read_extract(struct archive *, struct archive_entry *, + int flags); +diff --git a/libarchive/archive_write_disk.3 b/libarchive/archive_write_disk.3 +index fa925cc..a2e7afa 100644 +--- a/libarchive/archive_write_disk.3 b/libarchive/archive_write_disk.3 +@@ -177,6 +177,9 @@ The default is to not refuse such paths. + Note that paths ending in + .Pa .. + always cause an error, regardless of this flag. ++.It Cm ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS ++Refuse to extract an absolute path. ++The default is to not refuse such paths. + .It Cm ARCHIVE_EXTRACT_SPARSE + Scan data for blocks of NUL bytes and try to recreate them with holes. + This results in sparse files, independent
Bug#770414: unblock: gtk+3.0/3.14.5-1
Hello Niels!
I'd be more then happy if someone else could answer your questions
but I'll make an attempt at filling in some information here
just in case noone else steps up.
On Sat, Nov 29, 2014 at 10:48:06AM +0100, Niels Thykier wrote:
[...]
> > diff -Nru glib2.0-2.42.0/gio/gdbus-2.0/codegen/config.py
> > glib2.0-2.42.1/gio/gdbus-2.0/codegen/config.py
> > --- glib2.0-2.42.0/gio/gdbus-2.0/codegen/config.py 2014-09-22
> > 17:18:16.0 +
> > +++ glib2.0-2.42.1/gio/gdbus-2.0/codegen/config.py 2014-11-09
> > 23:20:38.0 +
> > @@ -21,5 +21,5 @@
> >
> > DATADIR = "${prefix}/share"
> > DATADIR = DATADIR.replace(
> > -"${prefix}", "/usr/local")
> > -VERSION = "2.42.0"
> > +"${prefix}", "/home/mclasen/gnome")
> > +VERSION = "2.42.1"
>
> Is the above going to be an issue/break stuff?
The above is a generated file built from config.py.in, so should not be
any issue here.
>
> > diff -Nru glib2.0-2.42.0/gio/gioenums.h glib2.0-2.42.1/gio/gioenums.h
> > --- glib2.0-2.42.0/gio/gioenums.h 2014-09-22 13:42:12.0 +
> > +++ glib2.0-2.42.1/gio/gioenums.h 2014-10-02 18:02:20.0 +
> > [...]
> > @@ -1377,9 +1377,9 @@
> >G_CREDENTIALS_TYPE_INVALID,
> >G_CREDENTIALS_TYPE_LINUX_UCRED,
> >G_CREDENTIALS_TYPE_FREEBSD_CMSGCRED,
> > - G_CREDENTIALS_TYPE_NETBSD_UNPCBID,
> >G_CREDENTIALS_TYPE_OPENBSD_SOCKPEERCRED,
> > - G_CREDENTIALS_TYPE_SOLARIS_UCRED
> > + G_CREDENTIALS_TYPE_SOLARIS_UCRED,
> > + G_CREDENTIALS_TYPE_NETBSD_UNPCBID
> > } GCredentialsType;
> >
> > /**
>
> Is this a public enum with values re-ordered for no apparent reason (and
> possibly breaking ABI)?
Yes, except the "for no apparent reason" part.
The introduction of NetBSD support caused an ABI breakage, this simply
reverts to the old ABI. This likely does not affect us at all though
(since it involves NetBSD, OpenBSD and Solaris).
Regards,
Andreas Henriksson
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141129144942.ga12...@fatal.se
Bug#771660: unblock: rygel/0.24.2-1 (pre-approval)
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello Release-Team!
I'd like to update rygel to 0.24.2. This release has
two bugfixes.
https://git.gnome.org/browse/rygel/commit/?h=rygel-0-24&id=e34b0a8af3355512b31af3456da1a79c4d8c69d4
https://git.gnome.org/browse/rygel/commit/?h=rygel-0-24&id=b307ee367b4e388e1b197bcb0d7d82cd0de4f697
https://git.gnome.org/browse/rygel/commit/?h=rygel-0-24&id=82c43b7c5608d79ed815b9d1f3c4f49598bcedcd
The full upstream vcs diff is attached. (This will also result in generated
files being updated, which I assume release-team doesn't want to look at.)
If approving, please eventually unblock package rygel
unblock rygel/0.24.2-1
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (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_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/NEWS b/NEWS
index e5ec374..18661c8 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,18 @@
+0.24.2
+==
+
+A maintenance release of Rygel!
+
+Server:
+ - Fix sidecar album art extraction.
+
+Media-Export:
+ - Work-around an issue with GStreamer bindings that caused truncated embedded
+ album art.
+
+All contributors to this release:
+ - Jens Georg
+
0.24.1
==
diff --git a/src/librygel-server/rygel-media-art-store.vala b/src/librygel-server/rygel-media-art-store.vala
index 5d939f1..6b5281b 100644
--- a/src/librygel-server/rygel-media-art-store.vala
+++ b/src/librygel-server/rygel-media-art-store.vala
@@ -113,8 +113,22 @@ public class Rygel.MediaArtStore : GLib.Object {
}
try {
-media_art_process.buffer (MediaArt.Type.ALBUM, MediaArt.ProcessFlags.NONE, file,
- data, item.mime_type, item.artist, item.album);
+if (data != null) {
+string? mime = null;
+this.media_art_process.buffer (MediaArt.Type.ALBUM,
+ MediaArt.ProcessFlags.NONE,
+ file,
+ data,
+ mime,
+ item.artist,
+ item.album);
+} else {
+this.media_art_process.file (MediaArt.Type.ALBUM,
+ MediaArt.ProcessFlags.NONE,
+ file,
+ item.artist,
+ item.album);
+}
} catch (Error error) {
warning ("%s", error.message);
}
diff --git a/src/plugins/media-export/rygel-media-export-item-factory.vala b/src/plugins/media-export/rygel-media-export-item-factory.vala
index ae71f40..cbd0f35 100644
--- a/src/plugins/media-export/rygel-media-export-item-factory.vala
+++ b/src/plugins/media-export/rygel-media-export-item-factory.vala
@@ -294,7 +294,12 @@ namespace Rygel.MediaExport.ItemFactory {
case Tag.ImageType.FRONT_COVER:
Gst.MapInfo map_info;
sample.get_buffer ().map (out map_info, Gst.MapFlags.READ);
-store.add (item, file, map_info.data);
+
+// Work-around bgo#739915
+weak uint8[] data = map_info.data;
+data.length = (int) map_info.size;
+
+store.add (item, file, data);
sample.get_buffer ().unmap (map_info);
break;
default:
Bug#771660: unblock: rygel/0.24.2-1
Control: tags -1 - moreinfo
Hello Ivo De Decker!
On Sat, Dec 06, 2014 at 06:25:33PM +0100, Ivo De Decker wrote:
[...]
> Please go ahead and upload the package. Once that's done, remove the moreinfo
> tag and provide a filtered diff (with an explanation of what was filtered and
> why).
Thanks. Uploaded. Please unblock.
Filtered debdiff, excluding all generated files, generated by:
debdiff /var/cache/pbuilder/result/rygel_0.24.[12]-1.dsc | filterdiff -i
'*.vala' -i '*/NEWS'
--- rygel-0.24.1/NEWS 2014-10-13 21:11:08.0 +0200
+++ rygel-0.24.2/NEWS 2014-11-10 20:33:25.0 +0100
@@ -1,3 +1,18 @@
+0.24.2
+==
+
+A maintenance release of Rygel!
+
+Server:
+ - Fix sidecar album art extraction.
+
+Media-Export:
+ - Work-around an issue with GStreamer bindings that caused truncated embedded
+ album art.
+
+All contributors to this release:
+ - Jens Georg
+
0.24.1
==
--- rygel-0.24.1/src/librygel-server/rygel-media-art-store.vala 2014-10-12
13:23:28.0 +0200
+++ rygel-0.24.2/src/librygel-server/rygel-media-art-store.vala 2014-11-10
20:23:18.0 +0100
@@ -113,8 +113,22 @@
}
try {
-media_art_process.buffer (MediaArt.Type.ALBUM,
MediaArt.ProcessFlags.NONE, file,
- data, item.mime_type, item.artist,
item.album);
+if (data != null) {
+string? mime = null;
+this.media_art_process.buffer (MediaArt.Type.ALBUM,
+ MediaArt.ProcessFlags.NONE,
+ file,
+ data,
+ mime,
+ item.artist,
+ item.album);
+} else {
+this.media_art_process.file (MediaArt.Type.ALBUM,
+ MediaArt.ProcessFlags.NONE,
+ file,
+ item.artist,
+ item.album);
+}
} catch (Error error) {
warning ("%s", error.message);
}
--- rygel-0.24.1/src/plugins/media-export/rygel-media-export-item-factory.vala
2014-10-12 13:23:29.0 +0200
+++ rygel-0.24.2/src/plugins/media-export/rygel-media-export-item-factory.vala
2014-11-10 20:24:41.0 +0100
@@ -294,7 +294,12 @@
case Tag.ImageType.FRONT_COVER:
Gst.MapInfo map_info;
sample.get_buffer ().map (out map_info, Gst.MapFlags.READ);
-store.add (item, file, map_info.data);
+
+// Work-around bgo#739915
+weak uint8[] data = map_info.data;
+data.length = (int) map_info.size;
+
+store.add (item, file, data);
sample.get_buffer ().unmap (map_info);
break;
default:
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141206182005.ga29...@fatal.se
Bug#772982: unblock: util-linux/2.25.2-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package util-linux
The latest upload fixes 2 RC bugs (one of them being security related)
and includes a whole lot of l10n updates thanks to David Prévot.
I'm attaching a filtered debdiff (excluding the actual language
string changes), plus the patch from upstream for the security
issue so you don't have to read patch-in-patch if you don't want to.
unblock util-linux/2.25.2-4
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (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_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
debdiff /var/cache/pbuilder/result/util-linux_2.25.2-[34].dsc | filterdiff -x '*/debian/patches/Update-*.patch' -x '*/debian/patches/Trivial-unfuzzy.patch'
diff -Nru util-linux-2.25.2/debian/changelog util-linux-2.25.2/debian/changelog
--- util-linux-2.25.2/debian/changelog 2014-11-17 11:25:26.0 +0100
+++ util-linux-2.25.2/debian/changelog 2014-12-12 18:26:14.0 +0100
@@ -1,3 +1,30 @@
+util-linux (2.25.2-4) unstable; urgency=medium
+
+ [ David Prévot ]
+ * Update POT and PO files and clean up .gmo files
+ * Update German translation, thanks to Mario Blättermann
+ * Update Spanish translation, thanks to Antonio Ceballos Roa
+ * Update French translation (Closes: #770506)
+ * Update Ukrainian translation, thanks to Yuri Chornoivan
+ * Update Brazilian Portuguese translation, thanks to Rafael Ferreira
+ * Update Chinese (simplified) translation, thanks to Wylmer Wang
+ * Update Danish translation, thanks to Joe Hansen
+ * Update Finnish translation, thanks to Lauri Nurmi
+ * Update Japanese translation, thanks to Takeshi Hamasaki
+ * Update Russian translation, thanks to Pavel Maryanov
+ * Trivial unfuzzy
+
+ [ Andreas Henriksson ]
+ * Add debian/patches/libblkid-care-about-unsafe-chars-in-cache.patch
+- from upstream git master commit 89e90ae7
+ "libblkid: care about unsafe chars in cache"
+- This fixes CVE-2014-9114: blkid command injection
+ see https://security-tracker.debian.org/tracker/CVE-2014-9114
+Thanks to Salvatore Bonaccorso (Closes: #771274)
+ * libuuid1: add passwd dependency for user migration (Closes: #771092)
+
+ -- Andreas Henriksson Fri, 12 Dec 2014 18:23:24 +0100
+
util-linux (2.25.2-3) unstable; urgency=medium
* Ship fstrim timer/service units as examples only (Closes: #767194)
diff -Nru util-linux-2.25.2/debian/clean util-linux-2.25.2/debian/clean
--- util-linux-2.25.2/debian/clean 1970-01-01 01:00:00.0 +0100
+++ util-linux-2.25.2/debian/clean 2014-12-12 18:26:14.0 +0100
@@ -0,0 +1 @@
+po/*.gmo
diff -Nru util-linux-2.25.2/debian/control util-linux-2.25.2/debian/control
--- util-linux-2.25.2/debian/control 2014-11-17 11:25:26.0 +0100
+++ util-linux-2.25.2/debian/control 2014-12-12 18:26:14.0 +0100
@@ -208,7 +208,7 @@
Architecture: any
Section: libs
Pre-Depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: passwd, ${misc:Depends}, ${shlibs:Depends}
Recommends: uuid-runtime
Replaces: e2fsprogs (<< 1.34-1)
Multi-Arch: same
diff -Nru util-linux-2.25.2/debian/patches/libblkid-care-about-unsafe-chars-in-cache.patch util-linux-2.25.2/debian/patches/libblkid-care-about-unsafe-chars-in-cache.patch
--- util-linux-2.25.2/debian/patches/libblkid-care-about-unsafe-chars-in-cache.patch 1970-01-01 01:00:00.0 +0100
+++ util-linux-2.25.2/debian/patches/libblkid-care-about-unsafe-chars-in-cache.patch 2014-12-12 18:26:14.0 +0100
@@ -0,0 +1,163 @@
+From: Karel Zak
+Date: Thu, 27 Nov 2014 13:39:35 +0100
+Subject: libblkid: care about unsafe chars in cache
+
+The high-level libblkid API uses /run/blkid/blkid.tab cache to
+store probing results. The cache format is
+
+ devname
+
+and unfortunately the cache code does not escape quotation marks:
+
+ # mkfs.ext4 -L 'AAA"BBB'
+
+ # cat /run/blkid/blkid.tab
+ ...
+ /dev/sdb1
+
+such string is later incorrectly parsed and blkid(8) returns
+nonsenses. And for use-cases like
+
+ # eval $(blkid -o export /dev/sdb1)
+
+it's also insecure.
+
+Note that mount, udevd and blkid -p are based on low-level libblkid
+API, it bypass the cache and directly read data from the devices.
+
+The current udevd upstream does not depend on blkid(8) output at all,
+it's directly linked with the library and all unsafe chars are encoded by
+\x notation.
+
+ # mkfs.ext4 -L 'X"`/tmp/foo` "' /dev/sdb1
+ # udevadm info --export-db | grep LABEL
+ ...
+ E: ID_FS_LABEL=X__/tmp/foo___
+ E: ID_FS_LABEL_ENC=X\x22\x60\x2ft
Pre-approval for gupnp-packages.
Hi release team, I'm seeking pre-approval of the following package updates that I'd like to see enter squeeze. * gupnp - minimal upstream bugfix release. - update available in debian experimental for review. For your convenience, here's the link to description of upstream changes: http://gitorious.org/gupnp/gupnp/commit/8b05c6d406e6b02f3d30eb9f8ea146e7b908eff5 * gupnp-av - minimal upstream bugfix release. - update available in debian experimental for review. - (will sneak in a fixed debian/watch file as a bonus.) For your convenience, here's the link to description of upstream changes: http://gitorious.org/gupnp/gupnp-av/commit/5b1f97996a7abac87f4e95818cccecba0439c214 * gupnp-dlna - low impact update, mainly bugfixes, no users in squeeze. - update available in debian experimental for review. For your convenience, here's the link to description of upstream changes (see 0.3.0 + 0.3.1): http://gitorious.org/gupnp/gupnp-dlna/blobs/master/NEWS Are these ok to upload to unstable and can I expect you to unblock for squeeze? -- Andreas Henriksson signature.asc Description: Digital signature
Re: Pre-approval for gupnp-packages.
Doh! Ofcourse I had to time my pre-approval request right before a new set of upstream bugfix releases where finally released. I'm updating my request with new versions of gupnp, gupnp-av, adding gssdp, and gupnp-dlna stays the same. I've prepared the updated packages in git but not uploaded anywhere yet. Hopefully you find using git to review the changes working for you, so here are some links to point out where you'll find things: * gssdp: http://git.debian.org/?p=collab-maint/gssdp.git;a=shortlog;h=refs/heads/debian-experimental http://git.debian.org/?p=collab-maint/gssdp.git;a=blob;f=NEWS;h=d222e10b7866db849ff41108c38c7cc87ae332c1;hb=refs/heads/upstream-experimental * gupnp: http://git.debian.org/?p=collab-maint/gupnp.git;a=blob;f=NEWS;h=cb4e6291147df8f873934576db4cfb45e27e68ea;hb=refs/heads/upstream-experimental http://git.debian.org/?p=collab-maint/gupnp-av.git;a=shortlog;h=refs/heads/debian-experimental * gupnp-av: http://git.debian.org/?p=collab-maint/gupnp-av.git;a=shortlog;h=refs/heads/debian-experimental http://git.debian.org/?p=collab-maint/gupnp-av.git;a=blob;f=NEWS;h=966e33beb5a3102a54dc06d1f11f6f6efff0d9c3;hb=refs/heads/upstream-experimental * gupnp-dlna (no change from last request, but here are the links anyway): http://git.debian.org/?p=collab-maint/gupnp-dlna.git;a=shortlog;h=refs/heads/debian-experimental http://git.debian.org/?p=collab-maint/gupnp-dlna.git;a=blob;f=NEWS;h=9ba258e13be8457eedef6bc1d1516f1b514a13e8;hb=refs/heads/upstream-experimental I'm hoping you agree with me that the upstream bugfixes would be a nice addition to squeeze and out-weighs any risk of breakage which should be very minimal. Regards, Andreas Henriksson signature.asc Description: Digital signature
Re: Pre-approval for gupnp-packages.
Hi Phillip Kern! On Sun, Oct 03, 2010 at 10:25:35AM +0200, Philipp Kern wrote: > (I did review the git branches debian-experimental against the current > unstable > version, which is the same as testing in all cases.) (Thats correct, no uploads to unstable since the freeze. I actually went ahead and uploaded to experimental, so reviewing either git or experimental is fine.) > > On Thu, Sep 16, 2010 at 07:18:27PM +0200, Andreas Henriksson wrote: > > * gssdp: > > > > http://git.debian.org/?p=collab-maint/gssdp.git;a=shortlog;h=refs/heads/debian-experimental > > > > http://git.debian.org/?p=collab-maint/gssdp.git;a=blob;f=NEWS;h=d222e10b7866db849ff41108c38c7cc87ae332c1;hb=refs/heads/upstream-experimental > > This is ok, as gssdp-socket-source.h isn't installed. > Thanks! > > * gupnp: > > > > http://git.debian.org/?p=collab-maint/gupnp.git;a=blob;f=NEWS;h=cb4e6291147df8f873934576db4cfb45e27e68ea;hb=refs/heads/upstream-experimental > > > > http://git.debian.org/?p=collab-maint/gupnp-av.git;a=shortlog;h=refs/heads/debian-experimental > > As there were no symbols files for the old one in unstable: are you sure there > are no disappearing symbols? (Maybe gupnp_context_manager_finalize...) If Upstream seems to have a very good clue when it comes to ABI. c.f. gupnp-av and the introduction of the _size64 function rather then fixing (and breaking ABI of) the _size function, for large file support on 32bit arches. That was done intentionally to avoid ABI breakage. gupnp_context_manager_finalize was static, so it shouldn't affect the ABI. (The good upstream ABI clue might be related to our fellow DD, Ross Burton, is (part of) upstream. :)) > people could stop reindent files, that would be helpful, too. gvalue-util.c > doesn't make me happy. Using strtoul instead of atoi... why?[1] While the page you refer to points out some flaws with strtoul, atoi really isn't any better. It's probably of questional "bug fix" value though, just like the reindentation... > > The other changes look fine. > Thanks! > > * gupnp-av: > > > > http://git.debian.org/?p=collab-maint/gupnp-av.git;a=shortlog;h=refs/heads/debian-experimental > > > > http://git.debian.org/?p=collab-maint/gupnp-av.git;a=blob;f=NEWS;h=966e33beb5a3102a54dc06d1f11f6f6efff0d9c3;hb=refs/heads/upstream-experimental > > Looks ok. > Thanks! > > * gupnp-dlna (no change from last request, but here are the links anyway): > > > > http://git.debian.org/?p=collab-maint/gupnp-dlna.git;a=shortlog;h=refs/heads/debian-experimental > > > > http://git.debian.org/?p=collab-maint/gupnp-dlna.git;a=blob;f=NEWS;h=9ba258e13be8457eedef6bc1d1516f1b514a13e8;hb=refs/heads/upstream-experimental > > There isn't a GNU Lesser General Public License version 2, right? That > replacement seems to be made of fail. Didn't review more, sorry. The license change (which probably is just a clarification of the original intent) is one of the reasons why I'd like to avoid shipping the old version. As for if a 2.0 version exists, most people still don't seem to tell Library or Lesser GPL apart, so my interpretation would be: http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html I don't want you to waste time on reviewing this package. I think it's completely harmless to update it since it has no reverse dependencies in debian. If you're still not convinced, I might go ask for a removal instead of supporting the 0.2 version of gupnp-dlna through the squeeze lifetime. Newer versions is already a requirement of known users anyway. > > Kind regards, > Philipp Kern > > [1] > http://synflood.at/blog/index.php?/archives/741-strtoul-considered-harmful.html I'll go ahead and upload everything to unstable now (and get back to you for the unblocks when ready). If you come to the conclusion after a full gupnp-dlna review that it's unsuitable, I'll go for a removal from squeeze for gupnp-dlna. Thanks again for reviewing! -- Andreas Henriksson signature.asc Description: Digital signature
Re: Pre-approval for gupnp-packages.
On Sun, Oct 03, 2010 at 04:25:19PM +0200, Philipp Kern wrote: > Hi, > > On Sun, Oct 03, 2010 at 04:14:09PM +0200, Andreas Henriksson wrote: > > > As there were no symbols files for the old one in unstable: are you sure > > > there > > > are no disappearing symbols? (Maybe gupnp_context_manager_finalize...) > > > If > > > > Upstream seems to have a very good clue when it comes to ABI. > > c.f. gupnp-av and the introduction of the _size64 function rather then > > fixing > > (and breaking ABI of) the _size function, for large file support on > > 32bit arches. That was done intentionally to avoid ABI breakage. > > > > gupnp_context_manager_finalize was static, so it shouldn't affect the ABI. > > > > (The good upstream ABI clue might be related to our fellow DD, Ross Burton, > > is (part of) upstream. :)) > > Ok then. > > > > people could stop reindent files, that would be helpful, too. > > > gvalue-util.c > > > doesn't make me happy. Using strtoul instead of atoi... why?[1] > > > > While the page you refer to points out some flaws with strtoul, atoi really > > isn't any better. It's probably of questional "bug fix" value though, just > > like the reindentation... > > Ok. > > > > There isn't a GNU Lesser General Public License version 2, right? That > > > replacement seems to be made of fail. Didn't review more, sorry. > > > > The license change (which probably is just a clarification of the original > > intent) is one of the reasons why I'd like to avoid shipping the old > > version. > > > > As for if a 2.0 version exists, most people still don't seem to tell > > Library or Lesser GPL apart, so my interpretation would be: > > http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html > > The point is that COPYING is actually taking about the Lesser 2.1. So they > should name the correct license (which they are free to relicense it to) in > the > license headers. > > Furthermore you now install dlna profiles, whatever they are. I'm not really > able to review the XML changes, and they weren't previously used in the > package? The installed dlna profiles files are machine readable xml files which try to define the rules for when a media file belongs to a certain "profile" in the (secret) DLNA standard. Unless you have access to the DLNA standard doc, I see no way for you (or me) to review the profiles. > > And in general it looks like a too big diff to review. ): Ok, will file for removal. > > Kind regards, > Philipp Kern > -- Andreas Henriksson signature.asc Description: Digital signature
Bug#599027: RM: gupnp-dlna/0.2.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Given the vote of non-confidence of updating gupnp-dlna in squeeze, I'd hereby like to request the removal of the current version from squeeze. gupnp-dlna has no known reverse dependencies in squeeze. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (300, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101003205536.25024.7684.report...@amd64.fatal.se
Re: Pre-approval for gupnp-packages.
Hi! gssdp, gupnp, gupnp-av have all been uploaded and built on all archs now, so please unblock their testing migration. Thanks! -- Andreas Henriksson signature.asc Description: Digital signature
Bug#639871: gupnp transition also needs to include newer gupnp-igd
Hello! It's become apparent that gupnp-igd 0.1.x (current version in debian) breaks with gupnp 0.18.x. The fix is released as gupnp-igd 0.2.x which also bumps soname. $ grep-dctrl -sPackage -i -r -F Build-Depends,Build-Depends-Indep "\blibgupnp-igd-1.0-dev\b" /var/lib/apt/lists/*_Sources | sort -u Package: amsn Package: farsight2 Package: libnice Package: sushi I've spoken to bigon about updating it (in experimental for now)... Someone please update the transition tracker! (And could we start the transition soon? Please? Pretty Please?) -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111206123547.ga21...@amd64.fatal.se
Bug#639871: gupnp transition also needs to include newer gupnp-igd
Hello! On Fri, Dec 16, 2011 at 10:24:39AM +0100, Niels Thykier wrote: [...] > So far we have recorded the following SONAME/package name changes: > > libgssdp-1.0-2 => libgssdp-1.0-3 > libgupnp-1.0-3 => libgupnp-1.0-4 > libgupnp-igd-1.0-3 => libgupnp-igd-1.0-4 > > > And new one all appear to be ready in experimental already. However, in > the previous email, the following -dev packages were also mentioned: > > - libgupnp-av-1.0-dev >- Has a new version in experimental, but no SONAME change? yes > > - libgupnp-dlna-1.0-dev >- Nothing new in experimental build-dependencies already satisfied in unstable. > > So, will there be a sourceful upload of gupnp-av and gupnp-dlna bumping > their SONAME? no > > If not, I believe the tracker is curently up to date[1] and we should be > ready to start. Uploaded: gssdp, gupnp, gupnp-av, gupnp-vala, rygel ... (and gupnp-tools as a bonus while at it. new upstream release + IMHO no need to hold back gtk2 -> gtk3 switch anymore, so to unstable it went.) Still pending: gupnp-igd bigon didn't feel confortable enough with the testing of the new version yet. Please do *not* binNMU gupnp-igd even if it might seem possible by looking at dependencies, since runtime breakage has been mentioned by upstream Other binNMUs should be able to start as soon as the buildds have caught up with what was just uploaded -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111216151237.ga1...@amd64.fatal.se
Bug#780720: unblock: gnome-boxes/3.14.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gnome-boxes As discussed privately, jmm wanted to see fuseiso gone and gnome-boxes had an unneccesary/useless dependency on it. The new version simply drops the fuseiso dependency. unblock gnome-boxes/3.14.2-2 -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (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_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150318105158.31666.80289.report...@mbpah.endian.se
Bug#781163: util-linux 2.25.2-6 now uploaded, please unblock.
Control: retitle 781163 unblock (pre-approved): util-linux/2.25.2-6 Control: tags 781163 - moreinfo New/fixed version now uploaded. Please unblock. Thanks. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150329224903.gb12...@fatal.se
Bug#781726: how to solve the live-tools upgrade issue? (#781725)
Hello! Just adding my 5c here since I've previously been at the receiving end of the very same bug. On Thu, Apr 02, 2015 at 10:17:52AM +0200, Andreas Beckmann wrote: [...] > live-tools/wheezy is buggy, causing install/upgrade failures in other > packages (wheezy: #779888, upgrade: #781725). > The underlying dependency issue has been fixed in jessie long ago, Next stop - stable proposed update then?! > but that is not sufficient to get a working upgrade ordering without > adding Breaks against the buggy wheezy version somewhere: [...] > This happened because live-tools/jessie has not yet been unpacked and > instead the buggy replacement update-initramfs from live-tools/wheezy gets > used. > dmsetup is not required in a wheezy installation of live-tools, but gets > pulled in during the upgrade to jessie. > > This could be fixed (I verified this by building a patched lvm2 and using it > in a piuparts test) by adding > Breaks: Breaks: live-tools (<< 4.0.1-1) > to dmsetup to change the unpacking order and get rid of the broken live-tools > before configuring dmsetup, but that has been rejected by the lvm2 > maintainer (#778828). I think spreading workarounds for this issue all over the archive is not very nice. If anything, we should have a stronger policy against packages diverting stuff and not allow them in the archive without multiple developers supporting their existance and making sure bugs like the one in live-tools does not exist. If you really want to solve this and similar issues in a generic way for the future I'd suggest an extension to apt(itude) is developed to always pull in a meta-package first during dist-upgrade (or when it detects a new suite has been added during update). This meta-package can then carry all workarounds in one place. > > Note that removing live-tools from jessie won't solve this upgrade issue. I suggest simply documenting "aptitude purge live-tools" as one of the pre-upgrade checks to do prior to upgrading to Jessie in the release notes. You might argue that noone reads the release notes, but then they get what they deserve. Let user support forums deal with it. According to popcon the live-tools install-base is very marginal anyway. Regards, Andreas Henriksson PS. this was "solved" in util-linux by dropping the update-initramfs call given that initramfs-tools >= 0.117 did not make it into Jessie. Apparently now the new version has been allowed to migrate?! This means initramfs will contain outdated versions of files from util-linux. I've already had enough of this issue and will now simply stick my head in the sand and say that other people can deal with any issues related to initramfs (and util-linux). -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150402092756.ga11...@fatal.se
