Re: Bug#1034016: unblock (pre-approval): debos/1.1.1-2.1

[Andreas Henriksson]

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

Re: Bug#1034016: unblock (pre-approval): debos/1.1.1-2.1

[Andreas Henriksson]

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.

Bug#1034016: unblock (pre-approval): debos/1.1.1-2.1

[Andreas Henriksson]

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-Simple-exampl.

Bug#1022003: transition: gssdp/gupnp 1.6: Status update + prepared to start

[Andreas Henriksson]

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#1022003: transition: gssdp/gupnp 1.6: Status update + prepared to start

[Andreas Henriksson]

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.2->1.6 (+ rygel 0.42.0)

[Andreas Henriksson]

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=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.2->1.6 (+ rygel 0.42.0)

[Andreas Henriksson]

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_installed=on_vote=on_legend=on_ticks=on_date=_date=_date=_fmt=%25Y-%25m=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)

[Andreas Henriksson]

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)

[Andreas Henriksson]

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)

[Andreas Henriksson]

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#988473: unblock: gnome-sound-recorder/3.38.1-1

[Andreas Henriksson]

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 = upstream/3.38.x
 
 [buildpackage

Bug#984925: pre-approval: updating python-networkmanager to 2.2 (bugfix release) in bullseye

[Andreas Henriksson]

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#984925: pre-approval: updating python-networkmanager to 2.2 (bugfix release) in bullseye

[Andreas Henriksson]

= 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#942428: transition: gssdp/gupnp

[Andreas Henriksson]

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#933548: transition: gnome-desktop3

[Andreas Henriksson]

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#933548: transition: gnome-desktop3

[Andreas Henriksson]

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#933577: transition: evolution-data-server

[Andreas Henriksson]

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

[Andreas Henriksson]

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#933548: transition: gnome-desktop3

[Andreas Henriksson]

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#940460: transition: mutter

[Andreas Henriksson]

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#933577: transition: evolution-data-server

[Andreas Henriksson]

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#933548: transition: gnome-desktop3

[Andreas Henriksson]

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#940350: transition: libgweather

[Andreas Henriksson]

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

fix neomutt gpg integration NMU/pre-approval

[Andreas Henriksson]

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#926597: unblock: golang-github-puerkitobio-purell/1.1.0-2

[Andreas Henriksson]

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 struct {
+@

Bug#926585: unblock: shishi/1.0.2-6.2

[Andreas Henriksson]

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#924394: unblock: libqmi/1.22.0-1.2

[Andreas Henriksson]

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, )) == 0) ||
+ !qmi_message_tlv_read_guint8 (message, init_offset, , 
_tmp, ) ||
+ !qmi_message_tlv_read_guint8 (message, init_offset, , 
&(info.cid), )) {
+-- 
+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#859702: unblock: libarchive/3.2.2-2

[Andreas Henriksson]

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#859437: unblock: util-linux/2.29.2-1

[Andreas Henriksson]

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#859437: unblock: util-linux/2.29.2-1

[Andreas Henriksson]

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

Re: Draft for taging 32 RC bugs with can-defer, will-remove or is-blocker

[Andreas Henriksson]

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#853469: unblock: libarchive/3.2.1-6

[Andreas Henriksson]

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 <andr...@fatal.se>  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 <mar...@matuska.org>
+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(>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

Bug#797074: libical2 transition now ready to start!

[Andreas Henriksson]

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#797074: libical2 transition now ready to start!

[Andreas Henriksson]

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!

[Andreas Henriksson]

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 ftbfs bugs now filed

[Andreas Henriksson]

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

[Andreas Henriksson]

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#819979: libgit2 transition pending, now in experimental.

[Andreas Henriksson]

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#819979: libgit2 transition pending, now in experimental.

[Andreas Henriksson]

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: transition: libgit2

[Andreas Henriksson]

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#812887: transition: iptables

[Andreas Henriksson]

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#810961: quvi, totem-pl-parser and cclive uploaded starting (and finishing?) the transition.

[Andreas Henriksson]

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#800599: eds transition started, time for binNMUs

[Andreas Henriksson]

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#800599: eds transition started, time for binNMUs

[Andreas Henriksson]

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: transition: evolution-data-server 3.18

[Andreas Henriksson]

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: transition: evolution-data-server 3.18

[Andreas Henriksson]

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

[Andreas Henriksson]

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#797074: transition: libical

[Andreas Henriksson]

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 andr...@fatal.se  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#797074: transition: libical

[Andreas Henriksson]

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#795911: Upload of gtk+3.0/3.14.5-1+deb8u1 to Jessie will be accepted by the Stable Release Managers

[Andreas Henriksson]

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 ruben.undh...@gmail.com
+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 ruben.undh...@gmail.com
+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, TRUE,
+ NULL

Bug#781726: how to solve the live-tools upgrade issue? (#781725)

[Andreas Henriksson]

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

Bug#781163: util-linux 2.25.2-6 now uploaded, please unblock.

[Andreas Henriksson]

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#780720: unblock: gnome-boxes/3.14.2-2

[Andreas Henriksson]

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#779846: unblock: libarchive/3.1.2-11

[Andreas Henriksson]

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 andr...@fatal.se  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 alessan...@ghedini.me
+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 of whether the archive format
+diff --git a/libarchive

Bug#777163: unblock: gnome-control-center/1:3.14.2-3

[Andreas Henriksson]

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 andr...@fatal.se  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#776989: unblock: util-linux/2.25.2-5

[Andreas Henriksson]

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 andr...@fatal.se  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 gaud...@debian.org  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#772982: unblock: util-linux/2.25.2-4

[Andreas Henriksson]

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 andr...@fatal.se  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 k...@redhat.com
+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
+
+   device NAME=value ...devname/device
+
+and unfortunately the cache code does not escape quotation marks:
+
+   # mkfs.ext4 -L 'AAABBB'
+
+   # cat /run/blkid/blkid.tab
+   ...
+   device ... LABEL=AAABBB .../dev/sdb1/device
+
+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
+\xhex 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\x2ftmp\x2ffoo\x60\x20\x22
+
+Signed-off

Bug#771660: unblock: rygel/0.24.2-1

[Andreas Henriksson]

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 m...@jensge.org
+
 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#771660: unblock: rygel/0.24.2-1 (pre-approval)

[Andreas Henriksson]

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-24id=e34b0a8af3355512b31af3456da1a79c4d8c69d4
https://git.gnome.org/browse/rygel/commit/?h=rygel-0-24id=b307ee367b4e388e1b197bcb0d7d82cd0de4f697
https://git.gnome.org/browse/rygel/commit/?h=rygel-0-24id=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 m...@jensge.org
+
 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#770414: unblock: gtk+3.0/3.14.5-1

[Andreas Henriksson]

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#770414: unblock: gtk+3.0/3.14.5-1

[Andreas Henriksson]

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

[Andreas Henriksson]

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#770338: unblock: nautilus/3.14.1-1

[Andreas Henriksson]

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 andr...@fatal.se  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-private/nautilus-file-operations.c
--- nautilus-3.14.0/libnautilus

Bug#770338: unblock: nautilus/3.14.1-1

[Andreas Henriksson]

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

[Andreas Henriksson]

¡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#770204: unblock: gnome-logs/3.14.2-1

[Andreas Henriksson]

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 @@
 id type=desktoporg.gnome.Logs.desktop/id
 metadata_licenseCC0-1.0/metadata_license
 project_licenseGPL-3.0+/project_license
-!-- Both taken from desktop file.
-nameLogs/name
-summaryView detailed event logs for the system/summary
---
+!-- Name and summary taken from the desktop file. --
+_nameLogs/_name
+_summaryView detailed event logs for the system/_summary
 description
 _pLogs shows events from the systemd journal, and sorts them into
 categories, such as hardware and applications./_p
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 andr...@fatal.se  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

Bug#770204: unblock: gnome-logs/3.14.2-1

[Andreas Henriksson]

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#768315: uploaded, please unblock.

[Andreas Henriksson]

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#768315: unblock: util-linux/2.25.2-3

[Andreas Henriksson]

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

Re: Bug#769273: bsdutils: Dependency on libsystemd0 violates policy

[Andreas Henriksson]

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

[Andreas Henriksson]

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 andr...@fatal.se  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

[Andreas Henriksson]

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

[Andreas Henriksson]

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

reassign binNMU request to release.debian.org

[Andreas Henriksson]

Control: reassign -1 release.debian.org

Hello!

Apparently I filed by binNMU request for gtk+3.0 against the wrong
package, reassigning...

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/20140829075536.ga15...@fatal.se

Bug#759284: nmu: evolution_3.12.2-1+b1

[Andreas Henriksson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hello!

Because of gtkhtml4.0 shlibs having a strict lowest  highest allowed
versions all reverse dependencies have previously picked up a
 4.8 dependency.
Since gtkhtml4.0 4.8.4 was uploaded to the archive this meant that
a bunch of packages became uninstallable unfortunately.

Since the new gtkhtml4.0 includes updated shlibs, just rebuilding
the reverse dependencies should make them installable again.

This includes evolution, mail-notification and on some architectures
also libevolution.
(Also xiphos, but that is not part of testing and RC-buggy FTBFS.)

Lets see if I can get this right:

nmu evolution_3.12.2-1+b1 . ALL . -m Rebuild to bump gtkhtml4.0 dependencies 
to  4.10
nmu mail-notification_5.4.dfsg.1-12 . ALL . -m Rebuild to bump gtkhtml4.0 
dependencies to  4.10
nmu libevolution_3.12.5-1 . amd64 hurd-i386 mips powerpcspe ppc64 . -m Rebuild 
to bump gtkhtml4.0 dependencies to  4.10



-- 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.14-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


-- 
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/20140825200341.15096.27304.report...@mbpah.endian.se

Preparing (lib)gnome-keyring for the freeze.

[Andreas Henriksson]

Hello!

I wanted to discuss the (lib)gnome-keyring status and the state we
want it to be in before the freeze.

To sum up the current problem, the versions in unstable are RC-buggy
because of FTBFS. The FTBFS is caused by a newly introduced testsuite
which basically showed the package never worked on kFreeBSD.

There has been discussions about the use of mlock(all) and we have
over the past year not been able to reach a consensus. I don't
feel comfortable making the descision to rip out security features
on my own as proposed by porters and noone has been willing to take
the discussion upstream.

I don't think releasing with really old 3.4 versions is a good idea.

I seen two solutions, either ...

a/ accept that the software has never really worked on kfreebsd and remove
   the kfreebsd-any builds from testing.

b/ get back to the status quo by disabling the problematic tests on kfreebsd
   letting the package build and work equally as before.

My opinion is that because of how I interpret the part about hiding problems
in the social contract, (a) is preferrable.

If for some reason (a) is not possible, please tell me and I'll implement
(b).

For more background, see:
https://packages.qa.debian.org/libg/libgnome-keyring.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628383
https://packages.qa.debian.org/g/gnome-keyring.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750883

(As I see it, the gnome-keyring FTBFS is only because of libgnome-keyring
being non-functional and not a problem in gnome-keyring itself.)

Regards,
Andreas Henrikson


-- 
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/20140802064754.ga13...@fatal.se

Bug#751953: summary on upower transition, lets go?!

[Andreas Henriksson]

Hello!

A summary on the state of reverse dependencies of the upower
has been requested before starting the transition.

I'll attach my summary below and at the same time asks for
anyone who wishes for anything else before starting this
transition to speak up about that!


Except for razorqt and xfce, no replies from maintainers on either
call for action on debian-devel or the bug reports filed on their
packages. (Notable mention is that mate maintainers quickly uploaded
new version of their packages to fix build against libupower-glib-dev
. but didn't reply to dbus API bug report.)


Removals:
===

wmbattery: remove from testing.

sugar-session-0.96: others have suggested removal. Not checked.
sugar-session-0.98: --
sucrose-0.96: --
sucrose-0.98: --


NOPs (or removal if you prefer):
===

razorqt-power: razorqt dead upstream (merged with LXDE), sounds like it's
already not in shape for release.

cinnamon-session: only in experimental.

indicator-session: source seems to indicate suspend + hibernate
only via upower, but looks like it disables menu entries when upower
is not available.
indicator-session-gtk2: -- (built from same source)
Note: indicator-session* has no reverse dependencies.


Sourceful uploads:
===

cairo-dock-plug-ins: NMU with upower disabled for now.
Also tries both logind and ck besides upower interfaces.

gnome-applets: sponsor new package revision once transition starts.

xfce: response from maintainer Not sure what he's saying though and why
he's not picking up the patches from fedora. Might need NMU.
(xfce4-systemload-plugin: apparently fixed in svn)
(xfce4-session, xfce4-power-manager)


Remaining packages with open bug reports (NOPs?):
===

mate: api usage already fixed in mate, dbus-usage should hopefully not
be a problem? Assume maintainer has tested his previous work.
(mate-power-manager, mate-session-manager)

gnome: not checked but IMO not interesting since it'll be replaced by
gnome 3.12 components as soon as the upower transition has finished.
(gnome-power-manager, gdm3, gnome-session-bin)

lxsession: source seems to indicate support for both logind and upower.

lightdm: source seems to indicate upower is only a fallback after logind.

kde: not checked but KDE is generally a known user of logind interface...
(kde-config-touchpad, libsolid4, kde-plasma-desktop, kde-plasma-netbook)


-- 
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/20140706214447.ga27...@fatal.se

Bug#751953: transition: upower

[Andreas Henriksson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Filing this mostly as a placeholder for tracking purposes.

Bug reports has been filed for users of the C library API, see:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=upower-1.0;users=pkg-utopia-maintain...@lists.alioth.debian.org

From a transition point, those are pretty much done.
(Sponsor gnome-applets sourceful upload, temporarily remove wmbattery,
NMU cairo-dock-plug-ins disabling the upower backend which is only a fallback,
binNMU the rest.)

What remains unknown is how DBus users will be affected by this transition.
For example parts of the functionality (duplicated logind functionality mostly)
is no longer provided by the new UPower.
This query is probably useful to spot users of the DBus API:
http://codesearch.debian.net/search?q=%28%3Fi%29org%5C.freedesktop%5C.upower

The new upower has been sitting in experimental around 4 months now.
So far noone has got in contact about potential upgrade issues in their
packages.
I'm filing this bug report so that I can send out a call for people
to please verify there's no problem on their side and if there is they
can file a bug against their own package and set it as a blocker for
this bug report.



Ben file:

title = upower;
is_affected = .depends ~ libupower-glib1 | .depends ~ libupower-glib2;
is_good = .depends ~ libupower-glib2;
is_bad = .depends ~ libupower-glib1;


-- 
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/20140618083848.9457.51911.report...@mbpah.endian.se

Re: Bug#751052: RM: iproute -- ROM; Deprecated by src:iproute2

[Andreas Henriksson]

Hi all!

On Tue, Jun 10, 2014 at 07:44:24PM +0200, Emilio Pozuelo Monfort wrote:
 On 10/06/14 19:26, Niels Thykier wrote:
  Hi Andreas and FTP masters,
  
  Are we sure that ALL binaries from iproute are now built by iproute2?
  Personally, I am not convinced that iproute2 builds iproute-dev[1].

You're right Nils, iproute-dev is no longer built on purpose.

I helped port the last user, collectd, away from using it a long time ago.

There's no point in using a static library which only worked on a
limited set of 32bit architectures when there are so many other
proper libraries which works on all (linux) architectures available.

 
 I doesn't seem to, but nothing seems to depend or build-depend on it. So
 binary:iproute-dev probably needs to be removed as well.

Yes, please remove binary:iproute-dev if it isn't already gone.

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/20140610223931.ga2...@fatal.se

Re: gnome-terminal: FTBFS on kfreebsd hurd archs

[Andreas Henriksson]

Hello Robert Millan!

On Sat, May 31, 2014 at 03:43:18PM +0200, Robert Millan wrote:
 
 Hi,
 
 I find it very strange that a terminal application needs gnome-shell.
[...]

Maybe you should try to spend 2 seconds on trying to figure it out
(ie. by searching the package changelog) before posting in the future.

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/20140531155148.ga26...@fatal.se

Re: heads up: work needed on upower?

[Andreas Henriksson]

Hello Robert Millan!

Not sure what you're saying... I have no clue about BSD.

Things seems to work fine on FreeBSD however Maybe you can
find something of value here (where they apparenty put the work
on packaging GNOME 3.12 for FreeBSD, including UPower 0.99.x):
http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom/ports-experimental/trunk/sysutils/upower/

I don't know how to FreeBSD ports work, but the only patch I can find
(under files) is very trivial so things must have improved since
upower upstream sent their call for help

I spotted that the Debian experimental build of upower has failed
on kfreebsd...

make[6]: Entering directory `/«PKGBUILDDIR»/src/freebsd'
  CC   libupshared_la-up-acpi-native.lo
  CC   libupshared_la-up-backend.lo
In file included from up-backend.c:27:0:
/usr/include/kvm.h:82:1: error: unknown type name 'uint64_t'
 uint64_t  kvm_counter_u64_fetch(kvm_t *, u_long);
 ^
up-backend.c:323:1: warning: no previous declaration for 
'up_backend_get_used_swap' [-Wmissing-declarations]
 up_backend_get_used_swap (UpBackend *backend)
 ^
make[6]: *** [libupshared_la-up-backend.lo] Error 1


Looks like a missing #include stdint.h or something like that, no?


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/20140522152047.ga14...@pi.fatal.se

Re: heads up: work needed on upower?

[Andreas Henriksson]

Hello Robert Millan!

On Thu, May 22, 2014 at 06:18:26PM +0200, Robert Millan wrote:
 Yes. This is a typical porting issue (uintXX_t types are defined by 
 sys/types.h on FreeBSD,
 so their code often doesn't include stdint.h).

Thanks for this information... but again I'm not sure what you're saying.

We're talking about /usr/include/kvm.h here.. their code ?

(experimental_kfreebsd-amd64-dchroot)ah@falla:~$ dpkg -S /usr/include/kvm.h 
libkvm-dev: /usr/include/kvm.h

(experimental_kfreebsd-amd64-dchroot)ah@falla:~$ apt-cache show libkvm-dev | 
grep ^Maintainer
Maintainer: GNU/kFreeBSD Maintainers debian-...@lists.debian.org

I'm sorry if it's my bad english or any other reason that we're talking
past each other
I've attached a simple minimal test-case that might help avoid confusion.
Please try to compile test.c

If I have to I can work around the broken system headers, but I'd
rather not carry workaround patches for bugs that never gets properly
fixed... (I see lftp is still carrying it's workaround for broken
kfreebsd headers. That was a nasty one. Wonder if it's still needed.)
Constantly having to rebase a patch for all eternal future is alot
of annoying and boring work which I really don't want to be bothered
with.
Also I wonder if maing upower compile will actually make it work
on kfreebsd. Would appreciate anyone with interest in the architecture
to actually test it.

Regards,
Andreas Henriksson
#include kvm.h

int main (int argc, char **argv)
{
	return 0;
}

Bug#748535: transition: gnutls28

[Andreas Henriksson]

Hello!

On Tue, May 20, 2014 at 08:02:22PM +0200, Julien Cristau wrote:
 On Tue, May 20, 2014 at 19:47:48 +0200, Andreas Metzler wrote:
 
  On 2014-05-20 Julien Cristau jcris...@debian.org wrote:
   On Mon, May 19, 2014 at 19:04:43 +0200, Julien Cristau wrote:
On Sun, May 18, 2014 at 08:52:53 +0200, Andreas Metzler wrote:
  [...] 
Apparently loading both versions of gnutls in the same process leads to
crashes.  That screams at bugs in gnutls symbol versioning.  Are you
aware of such issues?
  
  BTW: Do you have a reference to (one of) these issues?
  
 Andreas Henriksson was having issues with totem-pl-parser.  IIRC he had
 a backtrace mixing the two gnutlses.  They're no longer on
 paste.debian.net though so I'm hoping he'll be able to fill the gaps :)
[...]

I don't have the backtrace anymore, but crossing over from gnutls26 to
gnutls28 happened via the _gnutls_rnd_ops.rnd structure/abstraction.


If you want to reproduce this, take the (broken) patch from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746641#37
and rebuild totem-pl-parser with it.
After installing the patched totem-pl-parser, start totem
and goto channels, click the magnifying glass icon in the top right
to search, click local in the search entry and pick YouTube
instead, enter random search word and press enter

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/20140520203207.gb9...@pi.fatal.se

Bug#725231: transition: rhythmbox

[Andreas Henriksson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hello!

I'd like to upload a newer version of rhythmbox, which includes
a bump of the soname of the core library.

Ben file:

title = rhythmbox;
is_affected = .depends ~ librhythmbox-core7 | .depends ~ librhythmbox-core8;
is_good = .depends ~ librhythmbox-core8;
is_bad = .depends ~ librhythmbox-core7;


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (300, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-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/20131003063442.5333.49330.report...@amd64.fatal.se

Bug#723569: transition: evolution-data-server 3.8 started.

[Andreas Henriksson]

On Tue, Sep 17, 2013 at 11:30:04PM +0200, Andreas Henriksson wrote:
[...]
 Following mbiebls excellent laid out plan. It's been smooth sailing so far
 and I've built the above packages. I'm ready to sign and upload.
 
 Does anyone see any reason to not start this transition right away?
 

As noone has objected, I've gone ahead and uploaded:

libgweather
gtkhtml4.0
evolution-data-server
evolution
telepathy-farstream
folks

More uploads will come soon


In the meantime, please feel free to investigate binNMUs for the following:

mail-notification
xiphos
ekiga
libreoffice
ktp-call-ui
telepathy-qt

-- 
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/20130919092034.ga16...@amd64.fatal.se

Bug#723569: transition: evolution-data-server 3.8 started.

[Andreas Henriksson]

Hello!

On Thu, Sep 19, 2013 at 07:08:34PM +0100, Adam D. Barratt wrote:
[...]
 fwiw, at least this Release Team member would rather you had waited.

I'm sorry you feel that way.

 
 Lack of active objection is not the same as implicit acceptance,
 particularly in a less than 48-hour time frame. There are transition
 requests that have been waiting quite a bit longer than eds (some of
 them for far too long, at least partly due to failings on our part).

It didn't seem to me like the eds transition would interfere with any
other. The poppler transition isn't ready to start according to the
information available and the suitesparse transition collides with
ongoing transitions. Please enlighten me if I've missed anything,
and please also see that it was not my intention to stand in the way
of anyone else.

If you need to spend your time on dealing with any other transition
that's fine with me.

If it's any relief to you I hope we'll have the eds transition in
good shape very soon.
Most packages has been uploaded, what remains are basically:
- wait to see if anyone is willing to review the gnome-panel
  update I've prepared in pkg-gnome svn before I upload it.
- wait for the maintainers who has responded to bug reports
  to act on the message they just got where I asked them to
  upload their fixed package to unstable.
- wait for a couple of more package maintainers to acknowledge
  a NMU of their packages.
- schedule binNMUs
- remove leaf packages which apparently noone care about.
- wait for slow architectures buildds to finish building.
I'm probably too optimistic but I hope we can finish this
within a few days. The binNMU of libreoffice and slow buildds
might make it more then a few days.

-- 
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/20130919182613.ga31...@amd64.fatal.se

Bug#723569: transition: evolution-data-server 3.8 removal candidates

[Andreas Henriksson]

Hello!

I've assembled a list of removal candidates:

evolution-mapi (FTBFS fixed in 3.8.5-1 from exp, blocked by samba4 / samba 
reunification, RM from testing for the time being)
evolution-exchange (FTBFS, dead upstream, superseded by evolution-ews, RM bug 
filed)
evolution-webcal (FTBFS, , unmaintained, dead upstream RM?)
dates (FTBFS) dropped in Ubuntu
eweouz (FTBFS) dropped in Ubuntu
hdate-applet (FTBFS) dropped in Ubuntu
ruby-revolution (FTBFS) dropped in Ubuntu
tasks (FTBFS) dropped in Ubuntu
sflphone (FTBFS - conflicting b-deps)
 http://bugs.debian.org/716855
syncevolution (FTBFS) needs upgrading to 1.2.99.4
jana (FTBFS - missing b-dep on libgconf2-dev)
gnome-phone-manager (FTBFS)
 https://launchpad.net/ubuntu/+source/gnome-phone-manager/+changelog


If anyone think it's worth delaying the transition over any of these,
please speak up (or even better send a fix to the package bug report).

-- 
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/20130917152250.ga27...@amd64.fatal.se

Bug#723569: transition: evolution-data-server 3.8 ready to start?!

[Andreas Henriksson]

Hello!

On Tue, Sep 17, 2013 at 04:04:56PM +0200, Michael Biebl wrote:
[...]
 The rough plan looks like this
 - Upload libgweather 3.8 and gtkhtml 4.6 to unstable (ready in
   experimental)
 - Upload evolution-data-server 3.8 to unstable (ready in experimental)
 - Upload evolution 3.8, folks 0.9 and telepathy-farstream 0.6 to
   unstable (ready in experimental)

Following mbiebls excellent laid out plan. It's been smooth sailing so far
and I've built the above packages. I'm ready to sign and upload.

Does anyone see any reason to not start this transition right away?

 - binNMU above packages
 - upload or remove the remaining packages:
[...]

(I've already posted my removal suggestions and I have a rough plan
for how to deal with the rest. I probably need to figure out a few details
along the way. I'll get back to you with binNMU requests.)

-- 
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/20130917213004.ga10...@amd64.fatal.se

Bug#709098: cogl/clutter transition started

[Andreas Henriksson]

Hello Release Team and others!

I've just uploaded cogl 1.14.0-2 and clutter 1.0_1.14.4-2 to unstable.
In other words, the cogl/clutter transition has been started.

Since gtksourceview3 has still not migrated, do NOT touch gnome-sushi which
would entangle these two transitions.

(According to the migration tracker, toonloop is the only other collision
but neither libglew1.9 or boost1.53 transition has started yet)

Feel free to schedule other binNMUs after your regular investigations,
but I repeat... do not touch gnome-sushi yet!

-- 
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/20130816172901.ga3...@amd64.fatal.se

Bug#710708: transitions for GNOME 3.8

[Andreas Henriksson]

On Tue, Aug 13, 2013 at 10:19:14AM +0200, Julien Cristau wrote:
 On Mon, Aug 12, 2013 at 20:06:16 +0200, Julien Cristau wrote:
[...]
  Holding off on giggle because it's 9/10 so I'll schedule it tomorrow
  assuming it migrates tonight, and on gedit-plugins waiting for gedit.
  
 Scheduled the last two now.  Everything else is already built.

Thanks!

All packages have now been rebuilt and we're just waiting for
gtksourceview3 and gobby-infinote to get old enough.
I'm already tired of waiting, so feel free to age to make it migrate. ;)

My plan is to upload cogl/clutter on friday (with or without the gtksourceview3
transition finished). As long as we avoid touching gnome-sushi the
transitions should not get entangled if I understand things correctly.

-- 
Andreas Henriksson


signature.asc
Description: Digital signature

Re: transitions for GNOME 3.8

[Andreas Henriksson]

Hello!

The with both of the gdl and gjs transitions out of the way, I've started
another one by uploading gtksourceview3.
I've also NMUed gobby-infinote with the needed fix. (And jcristau helped
out with dep-waits which should make sure it gets built against the new
gtksourceview version.)
Both uploads where made with medium urgency to move ahead a bit faster.

Please schedule binNMUs for the remaining packages!

PS. cogl/clutter transition is now in good shape and I'm hoping to start that
this friday if gtksourceview3 is done by then (because of the gnome-sushi
collision).

-- 
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/20130812155513.ga18...@amd64.fatal.se

Bug#709098: rebuild of cogl/clutter rdeps

[Andreas Henriksson]

Hello!

Michael Biebl asked me to look into if the reverse dependencies of
cogl/clutter 1.14 still builds since it was a while since it was
last tried.

Two new build failures where identified. One in clutter-gst and one
in evolution. Both now have solutions available.
Michael Biebl offered to take care of the evolution upload and
I'll take care of clutter-gst.

Two issues in evolution:
- Werror used during automake made it fail
- needs to use libxml2 accessor api to access structure members in caldav plugin

Issue in clutter-gst:
- Use of GLint (fix stolen from upstream git)

meta-gnome3 will also need a sourceful upload to change its
hardcoded dependency.

Fwiw, I've had to do the rebuild in 7 different levels, because of
the packages depending on each other.

tier0 (sourceful uploads):
cogl
clutter

tier1:
clutter-gesture
clutter-gst
clutter-gtk
clutter-imcontext
muffin
mutter

tier2:
gnome-boxes
gnome-sushi
libchamplain
pinpoint
toonloop
mx
ibus-client-clutter

tier3:
cheese
evolution
eog-plugins
scim

tier4:
gnome-control-center

tier5:
gnome-shell

tier6:
cinnamon
empathy

tier7:
emerillon

tier8 (missed packages, should probably be in tier1 or 2):
gtkpod

-- 
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/20130811165253.ga11...@amd64.fatal.se

Re: transitions for GNOME 3.8

[Andreas Henriksson]

Thanks for the update on gdl and gjs.

I've talked to mbiebl and the plan, as soon as the above transitions
have entered testing, is to start gtksourceview3 which is in good shape.

A single issue remains (Bug#718524) which pkern promised to take care of,
or it will need NMU. The rest should hopefully work out with binNMUs.

As you might have read already, we're looking into other transitions as well.
clutter/cogl should hopefully soon be in good shape and go right
after gtksourceview3.
The evolution transition will probably need a bit more work to sort out.
(See comments in http://titanpad.com/Ap2rGx93U2 for details.)
After that, the rest will probably go together
(gnome-desktop, gnome-shell, g-s-d, g-c-c etc).

-- 
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/20130811172236.ga31...@amd64.fatal.se

Bug#711275: transition: tracker

[Andreas Henriksson]

Hello Adam!

On Tue, Jul 30, 2013 at 01:05:55AM +0200, Andreas Henriksson wrote:
 On Mon, Jul 29, 2013 at 08:42:57PM +0100, Adam D. Barratt wrote:
 [...]
   * rygel is tracker 0.16 ready and should be binNMUable.
  
  There's #715132, which is marked pending. It's not a regression from
  testing, so not a blocker, but it would be nice to avoid binNMUing rygel
  just to have it re-uploaded right away.
 
 Please binNMU. I have no plans for immediate uploading to unstable.
 (The fix is pending on top of the experimental version, which will
 be uploaded to unstable when it's released as stable according to
 gnome 3.10 release schedule.)

Despite what I said above, I've made a sourceful upload by request
from Michael Biebl. Apparently you and him discussed the need for
this as buildds can't handle alternative build-dependencies.

-- 
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/2013073133.ga1...@amd64.fatal.se

Bug#709847: transition: libgnomekbd

[Andreas Henriksson]

On Mon, Jul 29, 2013 at 08:42:38PM +0100, Adam D. Barratt wrote:
 Apologies for the delay; please go ahead and let us know once the
 unstable upload has been made.

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/20130729222430.ga30...@amd64.fatal.se

Bug#711275: transition: tracker

[Andreas Henriksson]

On Mon, Jul 29, 2013 at 08:42:57PM +0100, Adam D. Barratt wrote:
[...]
  * rygel is tracker 0.16 ready and should be binNMUable.
 
 There's #715132, which is marked pending. It's not a regression from
 testing, so not a blocker, but it would be nice to avoid binNMUing rygel
 just to have it re-uploaded right away.

Please binNMU. I have no plans for immediate uploading to unstable.
(The fix is pending on top of the experimental version, which will
be uploaded to unstable when it's released as stable according to
gnome 3.10 release schedule.)

-- 
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/20130729230554.ga17...@amd64.fatal.se

Bug#709847: gnome-control-center 1:3.4.3.1-3

[Andreas Henriksson]

Hello!

I've just uploaded gnome-control-center 1:3.4.3.1-3 to unstable
fixing the previous FTBFS with libgoa-1.0-dev 3.8.x.

The new package has also been build-tested with libgnomekbd8.

Hopefully this eliminates all and any doubts that libgnomekbd8 can
be a quick and easy transition.

-- 
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/20130526180948.ga1...@amd64.fatal.se

Bug#709847: transition: libgnomekbd

[Andreas Henriksson]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hello!

I'd like to request a slot for taking care of a small transition
as part of the pkg-gnome team for libgnomekbd 3.6.0.
The new upstream release has bumped soname.

reverse-depends -b libgnomekbd-dev

Reverse-Build-Depends
=
* gnome-control-center
* gnome-screensaver
* gnome-settings-daemon


I've tried rebuilding the current versions in unstable of the above packages
(g-c-c 1:3.4.3.1-2, g-scr 3.4.1-1, g-s-d 3.4.2+git20121218.7c1322-3).

Unfortunately g-c-c currently FTBFS in unstable, because of libgoa-1.0-dev 3.8.


In file included from /usr/include/goa-1.0/goabackend/goabackend.h:32:0,
 from cc-online-accounts-panel.c:31:
/usr/include/goa-1.0/goabackend/goaprovider.h:141:14: note: expected 'struct 
GtkGrid *' but argument is of type 'struct GtkTable *'
cc-online-accounts-panel.c:383:34: error: too few arguments to function 
'goa_provider_show_account'


The fix is either to get the g-c-c version from experimental into unstable,
or something along the lines of:
https://mail.gnome.org/archives/commits-list/2012-April/msg07554.html

The other two packages rebuild fine against the new libgnomekbd.

If/when I get the go ahead with this transition I'll take care of getting
g-c-c to build in unstable again (if it hasn't already been resolved
by then).


Ben file:

title = libgnomekbd;
is_affected = .depends ~ libgnomekbd7 | .depends ~ libgnomekbd8;
is_good = .depends ~ libgnomekbd8;
is_bad = .depends ~ libgnomekbd7;


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (300, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-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/20130526001451.31400.13358.report...@amd64.fatal.se

Bug#689698: closed by Adam D. Barratt a...@adam-barratt.org.uk (Re: Bug#689698: please unblock gupnp stack)

[Andreas Henriksson]

[...]
 The diffs didn't turn out to be that big once a lot of the noise is
 filtered out. I've argued with myself a lot over this, but have finally
 settled on the side on unblocking the packages to get the
 interoperability fixes; I hope we don't end up with that being an issue
 in future.

Thanks for looking at it again.

 
 (On the subject of the future, presumably these sort of issues are
 likely to come up during wheezy's stable lifetime as well?)

You never know about the future, but as far as I'm aware no major
problems has been identified since  while at the same time
multiple certification has been approved.
Hopefully this means what we're going to ship will be in a pretty good shape!

 
 Regards,
 
 Adam

-- 
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/20130413184929.ga21...@amd64.fatal.se

Bug#704080: unblock: libarchive/3.0.4-3

[Andreas Henriksson]

On Fri, Apr 05, 2013 at 12:18:46PM +0200, Philipp Kern wrote:
 Hi,
 
 On Fri, Apr 05, 2013 at 03:21:43AM +0100, peter green wrote:
  Specifically it seems that s390x has not successfully built this
  package for some time (since before s390x stopped being considered a
  broken and fucked architecture). As a result the s390x package is
  out of date in both testing and unstable. Britney will not migrate
  the package if there are out of date binaries in unstable (even if
  there are also out of date binaries for the same package in
  testing). The cause of the build failures seems to be a testsuite
  failure. Afaict there are several options in this scenario.
 
 my personal guess is that there's probably nothing s390x-specific to it,
 it's probably broken with 64bit big endian. The d-ports build for
 sparc64 fails as well.

Please also note that the current version (available in experimental for now)
seems to build ok on s390x (but fails on other platforms instead)..
Using git bisect should help identify the needed relevant changes.

Help is welcome.

-- 
Andreas Henriksson


signature.asc
Description: Digital signature