Re: migration exception for mhap

[Afif Elghraoui]

على الأحد 24 تـمـوز 2016 ‫05:32، كتب Jonathan Wiltshire:
> On 2016-07-23 23:14, Afif Elghraoui wrote:
>>
>> mhap is arch:all. libssw-java contains Java bindings for its C library
>> and is not supported on i386. The dependencies are not broken. I hope
>> this is a clear enough explanation.
> 
> Yes, I know all that, but your dependencies are still broken. Your 
> package is uninstallable on any architecture other than amd64.
> 

I thought arch:all meant that the package doesn't have
architecture-dependent files, not that it's supposed to be usable on
every single one.

Barring porting libssw to i386 or reducing functionality of the package
to remove dependency on libssw, would you prefer that I declare mhap as
arch:any so that it only builds for architectures where it will be
installable? Then we'll have multiple copies of the exact same package
for amd64, kfreebsd-amd64, and x32.

> For performance reasons britney only tests installability on amd64 and 
> i386 (hence the message), otherwise the list would be much longer.
> 
> A package cannot migrate if it is not installable on the test 
> architectures.
> 

For the purposes of mhap, it is a package for scientific research and
would probably not be usable on i386 even if it could be installed
there. It requires more powerful processors than anything that is i386
that I am aware of (besides am64 CPUs posing as such, but the package
works on x32 anyway).

If you really want me to jump through this hoop, I will be disabling
some functionality of the mhap package. I'm hoping it won't come to this.

Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#831810: transition: libmicrohttpd

[Jonathan Wiltshire]

On 2016-07-23 20:30, Bertrand Marc wrote:

Hi,

Le 23/07/2016 à 11:56, Emilio Pozuelo Monfort a écrit :

On 23/07/16 11:35, Bertrand Marc wrote:

Do you think we could allow the libmicrohttpd transition ?


Yes. Go ahead.


Thanks ! I uploaded a new revision targeting unstable to
mentors [1] and I asked Holger Levsen (CC), my regular sponsor, to
upload it to unstable.

Cheers,
Bertrand

[1]
https://mentors.debian.net/debian/pool/main/libm/libmicrohttpd/libmicrohttpd_0.9.50-2.dsc


Rebuilds scheduled.

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

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

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits

Bug#832171: jessie-pu: package dietlibc/0.33~cvs20120325-6

[Adam D. Barratt]

On Sun, 2016-07-24 at 22:45 +0200, Christian Seiler wrote:
> On 07/24/2016 10:18 PM, Christian Seiler wrote:
[...]
> > and potentially minit,
> > depending on whether you want to remove it or not.
> 
> nmu minit_0.10-5 . ALL . jessie . -m "Security, rebuild against fixed 
> dietlibc"

Salvatore already pointed out that a binNMU won't be suitable there. If
there's going to be an update to minit, it'll need to be as a source
upload, once a new dietlibc is available on all architectures.

Regards,

Adam

Bug#832171: jessie-pu: package dietlibc/0.33~cvs20120325-6

[Christian Seiler]

On 07/24/2016 10:18 PM, Christian Seiler wrote:
> On 07/23/2016 11:12 AM, Christian Seiler wrote:
>> Since dietlibc is a static library, after the upload, there will need
>> to be binNMUs in stable for the following three packages:
>>
>> nmu minit_0.10-5 . ALL . jessie . -m "Security: rebuild against fixed 
>> dietlibc"
>> nmu mksh_50d-5 . ALL . jessie . -m "Security: rebuild against fixed dietlibc"
>> nmu util-vserver_0.30.216-pre3054-1 . ALL . jessie . -m "Security: rebuild 
>> against fixed dietlibc"
> 
> Ok, that list got a bit shorter: Thorsten Glaser told me that while
> mksh Build-Depends on dietlibc-dev, it only uses it in sid onwards,
> so for Jessie there's no need to schedule a binNMU after the update
> to dietlibc for it.
> 
> So that would leave only util-vserver

And the wb-team just told me that a colon in the binNMU message
currently doesn't work on the buildds. Updated nmu strings for
after the upload of a fixed dietlibc:

nmu util-vserver_0.30.216-pre3054-1 . ALL . jessie . -m "Security, rebuild 
against fixed dietlibc"

> and potentially minit,
> depending on whether you want to remove it or not.

nmu minit_0.10-5 . ALL . jessie . -m "Security, rebuild against fixed dietlibc"

Regards,
Christian

Bug#832171: jessie-pu: package dietlibc/0.33~cvs20120325-6

[Christian Seiler]

On 07/23/2016 11:12 AM, Christian Seiler wrote:
> Since dietlibc is a static library, after the upload, there will need
> to be binNMUs in stable for the following three packages:
> 
> nmu minit_0.10-5 . ALL . jessie . -m "Security: rebuild against fixed 
> dietlibc"
> nmu mksh_50d-5 . ALL . jessie . -m "Security: rebuild against fixed dietlibc"
> nmu util-vserver_0.30.216-pre3054-1 . ALL . jessie . -m "Security: rebuild 
> against fixed dietlibc"

Ok, that list got a bit shorter: Thorsten Glaser told me that while
mksh Build-Depends on dietlibc-dev, it only uses it in sid onwards,
so for Jessie there's no need to schedule a binNMU after the update
to dietlibc for it.

So that would leave only util-vserver and potentially minit,
depending on whether you want to remove it or not.

Regards,
Christian

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: apache2_2.4.10-10+deb8u5_amd64.changes
  ACCEPT
Processing changes file: apache2_2.4.10-10+deb8u5_arm64.changes
  ACCEPT
Processing changes file: apache2_2.4.10-10+deb8u5_armel.changes
  ACCEPT
Processing changes file: apache2_2.4.10-10+deb8u5_armhf.changes
  ACCEPT
Processing changes file: apache2_2.4.10-10+deb8u5_i386.changes
  ACCEPT
Processing changes file: apache2_2.4.10-10+deb8u5_mips.changes
  ACCEPT
Processing changes file: apache2_2.4.10-10+deb8u5_mipsel.changes
  ACCEPT
Processing changes file: apache2_2.4.10-10+deb8u5_powerpc.changes
  ACCEPT
Processing changes file: apache2_2.4.10-10+deb8u5_ppc64el.changes
  ACCEPT
Processing changes file: apache2_2.4.10-10+deb8u5_s390x.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_multi.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_amd64.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_arm64.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_armel.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_armhf.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_i386.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_mips.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_mipsel.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_powerpc.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_ppc64el.changes
  ACCEPT
Processing changes file: mysql-5.5_5.5.50-0+deb8u1_s390x.changes
  ACCEPT
Processing changes file: mysql-connector-java_5.1.39-1~deb8u1_amd64.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_amd64.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_arm64.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_armel.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_armhf.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_i386.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_mips.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_mipsel.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_powerpc.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_ppc64el.changes
  ACCEPT
Processing changes file: openssh_6.7p1-5+deb8u3_s390x.changes
  ACCEPT
Processing changes file: phpmyadmin_4.2.12-2+deb8u2_amd64.changes
  ACCEPT
Processing changes file: python-django_1.7.7-1+deb8u5_amd64.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_amd64.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_arm64.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_armel.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_armhf.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_i386.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_mips.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_mipsel.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_powerpc.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_ppc64el.changes
  ACCEPT
Processing changes file: squid3_3.4.8-6+deb8u3_s390x.changes
  ACCEPT

Bug#832336: jessie-pu: package systemd/215-17+deb8u5

[Michael Biebl]

Am 24.07.2016 um 14:12 schrieb Michael Biebl:
> Package: release.debian.org
> Severity: normal
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Dear release team,
> 
> for the upcoming jessie stable release, I'd like to update the systemd
> package with the following fixes:

[..]

> The complete debdiff is attached as well.

I would like to include one more fix. The request for that came up just
today, see [1]. Sorry for the bad timing.

It's an upstream commit [2] which is part of v230 and ensures correct
shutdown order and kills the user sessions before the network stack is
stopped.
This is needed for open SSH connections to be terminated cleanly.

For this commit to apply cleanly, it also requires upstream commit [3],
which seems like a reasonable change as well.

An updated debdiff is attached.

Please let me know if you are ok with this updated debdiff.

Regards,
Michael



[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832155#50
[2]
https://github.com/systemd/systemd/commit/8c856804780681e135d98ca94d08afe247557770
[3]
https://github.com/systemd/systemd/commit/efb3e19be9c568974b221990b9e84fb5304c5537
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff --git a/debian/changelog b/debian/changelog
index 974bbb0..3f0f176 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,31 @@
+systemd (215-17+deb8u5) stable; urgency=medium
+
+  * Use the right timeout for stop processes we fork. This ensures that
+services are properly killed after a given timeout. (Closes: #813702)
+  * Re-enable fsck -l. This avoids that systemd-fsck runs fsck in parallel for
+file systems on the same disk. Parallel fsck can lead to suboptimal
+behaviour on rotational hard disks. This requires util-linux 2.25, so bump
+the dependency accordingly. (Closes: #824963)
+  * Don't reset log level to NOTICE if we get quiet on the kernel cmdline.
+(Closes: #828006)
+  * Fix prepare priority queue comparison function in sd-event.
+Otherwise a disabled event source can get swapped with an enabled one
+and cause a severe sd-event malfunction, breaking the event loop.
+(Closes: #789796)
+  * Update links to kernel.org cgroup documentation.
+The systemd.resource-control man page had references to /cgroups/ which
+moved to /cgroup-v1/. (Closes: #819970)
+  * Don't start console-getty.service when /dev/console is missing.
+Avoids repeated unsuccessful start attempts of agetty inside (docker)
+containers. (Closes: #829537)
+  * Order systemd-user-sessions.service after nss-user-lookup.target. We
+should not allow logins before NIS/LDAP users are available.
+  * Order systemd-user-sessions.service after network.target. That way we can
+be sure that local users are logged out and SSH sessions are ended cleanly
+before the network is shut down when the system goes down.
+
+ -- Michael Biebl   Sun, 24 Jul 2016 18:55:54 +0200
+
 systemd (215-17+deb8u4) stable; urgency=medium
 
   [ Martin Pitt ]
diff --git a/debian/control b/debian/control
index aa02024..cdcc5a4 100644
--- a/debian/control
+++ b/debian/control
@@ -51,7 +51,7 @@ Pre-Depends: ${shlibs:Pre-Depends},
 Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
- util-linux (>= 2.19.1-2),
+ util-linux (>= 2.25),
  mount (>= 2.21),
  initscripts (>= 2.88dsf-53.2),
  sysv-rc,
diff --git a/debian/extra/getty-static.service 
b/debian/extra/getty-static.service
index 8636be5..0a1203f 100644
--- a/debian/extra/getty-static.service
+++ b/debian/extra/getty-static.service
@@ -1,6 +1,6 @@
 [Unit]
 Description=getty on tty2-tty6 if dbus and logind are not available
-ConditionPathExists=/dev/tty2
+ConditionPathExists=/dev/tty0
 ConditionPathExists=!/lib/systemd/system/dbus.service
 
 [Service]
diff --git 
a/debian/patches/console-getty.service-don-t-start-when-dev-console-is-mis.patch
 
b/debian/patches/console-getty.service-don-t-start-when-dev-console-is-mis.patch
new file mode 100644
index 000..02eb1ca
--- /dev/null
+++ 
b/debian/patches/console-getty.service-don-t-start-when-dev-console-is-mis.patch
@@ -0,0 +1,49 @@
+From: Jan Pazdziora 
+Date: Fri, 13 Mar 2015 12:57:18 +0100
+Subject: console-getty.service: don't start when /dev/console is missing
+
+Create minimal image which runs systemd
+
+   FROM rhel7.1
+   RUN yum install -y /usr/bin/ps
+   ENV container docker
+   CMD [ "/usr/sbin/init" ]
+
+When you run the container without -t, the process
+
+   /sbin/agetty --noclear --keep-baud console 115200 38400 9600
+
+is not happy and checking the journal in the container, there is a stream of
+
+Mar 13 04:50:15 11bf07f59fff agetty[66]: /dev/console: No such file or 
directory
+Mar 13 04:50:25 11bf07f59fff systemd[1]: console-getty.service holdoff time 
over, scheduling restart.
+Mar 13 04:50:25 

Re: Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Francesco Poli]

On Sun, 24 Jul 2016 11:43:19 -0500 Don Armstrong wrote:

[...]
> I'll try to check out snapshots
> later this week to see if I can figure out when the transition actually
> happened, or if there was something else going on in the archive to
> explain it.

Thanks for your help!
Please keep us informed, as the investigations go on.

Bye.

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgphhxYGTKWnB.pgp
Description: PGP signature

Bug#831810: transition: libmicrohttpd

[Holger Levsen]

Hi Bertrand,

On Sat, Jul 23, 2016 at 09:30:22PM +0200, Bertrand Marc wrote:
> >> Do you think we could allow the libmicrohttpd transition ?
> > Yes. Go ahead.
> Thanks ! I uploaded a new revision targeting unstable to
> mentors [1]

thanks, uploaded to sid. 


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#830997: release.debian.org: Permission to consider dpkg-buildpackage -A bugs as RC

[Santiago Vila]

On Sun, 24 Jul 2016, Emilio Pozuelo Monfort wrote:

> On 23/07/16 19:20, Santiago Vila wrote:
>
> > Still ok to consider this as a release goal?
> 
> Absolutely.

Great, thanks!

On Wed, 20 Jul 2016, Lucas Nussbaum wrote:

> The additional bugs I filed are at:
>
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=qa-indep;users=debian...@lists.debian.org

To celebrate, I've created four tags to classify *all* the bugs:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=sanv...@debian.org;tag=arch-all-swapped-binary-targets
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=sanv...@debian.org;tag=arch-all-missing-build-indep
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=sanv...@debian.org;tag=arch-all-arch-any-missing-build-indep
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=sanv...@debian.org;tag=arch-all-arch-any-failing-binary-indep

This time it should be ok to add new bugs to those tags, because their
names are now clearly prefixed by either arch-all-arch-any or arch-all.

(The old tag, naively named "binary-indep" should be considered obsolete).

Thanks.

Re: Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Don Armstrong]

On Sun, 24 Jul 2016, Francesco Poli wrote:
> On Sun, 24 Jul 2016 16:24:19 +0100 Jonathan Wiltshire wrote:
> 
> > On 2016-07-24 16:00, Francesco Poli wrote:
> [...]
> > > Should  be contacted, perhaps?
> > 
> > Sure, if you'd like to.
> 
> Dear BTS owner,
> could you please investigate on what happened to bug #830267 on
> 2016-07-19T10:00 ?
> 
> Please take a look at
> https://bugs.debian.org/830267#20
> https://bugs.debian.org/830267#25
> for more context.

Hrm; it was shown as affecting testing at T0600 (and all subsequent
runs):

status-201607190600:number=830267
status-201607190600-testing=1
status-201607190600-unstable=1

but not on the immediately preceding run:

status-20160719:number=830267
status-20160719-testing=0
status-20160719-unstable=1

(You can check this out with grep -C 14 number=830267
/srv/bugs.debian.org/bugscan/stati/status-201607{19,20}*; on buxtehude or by
getting those status files from the web interface and examining them.)

That's really odd; I haven't changed anything on the BTS side during
that time period which would explain that happening.

Unfortunately, I don't know when the BTS thought that 1.18.9 was
actually in testing and not in unstable. I'll try to check out snapshots
later this week to see if I can figure out when the transition actually
happened, or if there was something else going on in the archive to
explain it.

-- 
Don Armstrong  https://www.donarmstrong.com

Americans can always be counted on to do the right thing, after they
have exhausted all other possibilities.
 -- W. Churchill

Re: Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Francesco Poli]

On Sun, 24 Jul 2016 16:24:19 +0100 Jonathan Wiltshire wrote:

> On 2016-07-24 16:00, Francesco Poli wrote:
[...]
> > Should  be contacted, perhaps?
> 
> Sure, if you'd like to.

Dear BTS owner,
could you please investigate on what happened to bug #830267 on
2016-07-19T10:00 ?

Please take a look at
https://bugs.debian.org/830267#20
https://bugs.debian.org/830267#25
for more context.

Thanks for your time.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpKh9__sDa55.pgp
Description: PGP signature

Re: Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Jonathan Wiltshire]

On 2016-07-24 16:00, Francesco Poli wrote:

I hope it's possible to investigate further, in order to find out what
really happened: needless to say, I think that the correctness of the
migration process is of great importance to the quality of Debian
testing (and, consequently, of future stable releases!).

Should  be contacted, perhaps?


Sure, if you'd like to.

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

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

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits

Re: Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Francesco Poli]

On Sun, 24 Jul 2016 13:51:45 +0100 Jonathan Wiltshire wrote:

> On 2016-07-24 11:20, Francesco Poli wrote:
[...]
> > Dear Release Team, could you please explain what I failed to understand
> > about the testing migration rules [2]?
> 
> Your understanding is correct - an RC bug affecting sid and not testing 
> is considered a regression and blocks migration, whereas one which 
> affects both suites does not.

Good, thanks for confirming!

> 
> Britney is fed that information from the BTS. The migration happened 
> because on 2016-07-18T22:00 #830267 was a regression, but on 
> 2016-07-19T10:00 it was marked as also affecting testing, so the package 
> was migrated. I don't know what happened in the BTS to cause that 
> change, certainly nothing on the bug log that I can see.

I hope it's possible to investigate further, in order to find out what
really happened: needless to say, I think that the correctness of the
migration process is of great importance to the quality of Debian
testing (and, consequently, of future stable releases!).

Should  be contacted, perhaps?


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpILBgo0ZFSQ.pgp
Description: PGP signature

Bug#832333: marked as done (nmu: sikulix_1.1.0-1~exp3)

[Debian Bug Tracking System]

Your message dated Sun, 24 Jul 2016 13:58:55 +0100
with message-id <9437ab558259338e5559bbe26691d...@hogwarts.powdarrmonkey.net>
and subject line Re: Bug#832333: nmu: sikulix_1.1.0-1~exp3
has caused the Debian Bug report #832333,
regarding nmu: sikulix_1.1.0-1~exp3
to be marked as done.

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

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


-- 
832333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu sikulix_1.1.0-1~exp3 . ANY . experimental . -m "Rebuild against 
libopencv-highgui2.4-deb0"

There was yet another opencv transition in sid ...

Andreas
--- End Message ---
--- Begin Message ---

On 2016-07-24 12:49, Andreas Beckmann wrote:

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

nmu sikulix_1.1.0-1~exp3 . ANY . experimental . -m "Rebuild against
libopencv-highgui2.4-deb0"

There was yet another opencv transition in sid ...


s/sid/experimental/ ? And it's now up to 3.0 for yay fun.

Scheduled, thanks.


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

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

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits--- End Message ---

Re: Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Jonathan Wiltshire]

On 2016-07-24 11:20, Francesco Poli wrote:
In the meanwhile, dpkg/1.18.9 managed to migrate to testing [1], 
despite

introducing this RC bug: I wonder how that was even possible... do the
testing migration checks skip pending RC bugs?!? a pending bug is not a
fixed bug!!! I am Cc-ing the Release Team about this.

Dear Release Team, could you please explain what I failed to understand
about the testing migration rules [2]?


Your understanding is correct - an RC bug affecting sid and not testing 
is considered a regression and blocks migration, whereas one which 
affects both suites does not.


Britney is fed that information from the BTS. The migration happened 
because on 2016-07-18T22:00 #830267 was a regression, but on 
2016-07-19T10:00 it was marked as also affecting testing, so the package 
was migrated. I don't know what happened in the BTS to cause that 
change, certainly nothing on the bug log that I can see.


It now, of course, correctly affects both sid and testing, so it is no 
longer a regression and further migrations will happen (notwithstanding 
other bugs affecting dpkg in sid).


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

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

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits

Bug#832336: jessie-pu: package systemd/215-17+deb8u5

[Michael Biebl]

Am 24.07.2016 um 14:12 schrieb Michael Biebl:
>   * Fix prepare priority queue comparison function in sd-event.
> Otherwise a disabled event source can get swapped with an enabled one
> and cause a severe sd-event malfunction, breaking the event loop.
> (Closes: #789796)
> 
> http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie=3272c6b98
> 
> 
> This patch has been cherry-picked from upstream. It was part of v227, so
> has seen quite a bit of testing in unstable/stretch.
> It's a rather annoying/important bug fix, because once systemd got in
> this confused state, it was busy looping and could hog your CPU.

This is probably the most invasive change, so I've provided test
packages at [1]. The feedback via IRC on via email was positive [2]

Regards,
Michael


[1] https://people.debian.org/~biebl/systemd/jessie/
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789796#112
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789796#117
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#828187: transition: rtmidi

[Jonathan Wiltshire]

On 2016-07-24 13:18, Jaromír Mikeš wrote:

all packages related to rtmidi transition are fixed and uploaded to
unstable.

Can I now upload rtmidi 2.1.1 to unstable?


Yes please.


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

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

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits

Bug#832336: jessie-pu: package systemd/215-17+deb8u5

[Michael Biebl]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Dear release team,

for the upcoming jessie stable release, I'd like to update the systemd
package with the following fixes:

systemd (215-17+deb8u5) stable; urgency=medium

  * Use the right timeout for stop processes we fork. This ensures that
services are properly killed after a given timeout. (Closes: #813702)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie=036d0949c

This patch has been cherry-picked from upstream. It was part of v217, so
has seen quite a bit of testing in unstable/stretch. Not aware of any
regressions caused by that change.

  * Re-enable fsck -l. This avoids that systemd-fsck runs fsck in parallel for
file systems on the same disk. Parallel fsck can lead to suboptimal
behaviour on rotational hard disks. This requires util-linux 2.25, so bump
the dependency accordingly. (Closes: #824963)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie=aca6f1a0a

This patch has been cherry-picked from upstream. It was part of v217, so
has seen quite a bit of testing in unstable/stretch. Not aware of any
regressions caused by that change.


  * Don't reset log level to NOTICE if we get quiet on the kernel cmdline.
(Closes: #828006)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie=c1bf59723

This patch has been cherry-picked from upstream. It was part of v219, so
has seen quite a bit of testing in unstable/stretch. Not aware of any
regressions caused by that change.


  * Fix prepare priority queue comparison function in sd-event.
Otherwise a disabled event source can get swapped with an enabled one
and cause a severe sd-event malfunction, breaking the event loop.
(Closes: #789796)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie=3272c6b98


This patch has been cherry-picked from upstream. It was part of v227, so
has seen quite a bit of testing in unstable/stretch.
It's a rather annoying/important bug fix, because once systemd got in
this confused state, it was busy looping and could hog your CPU.

  * Update links to kernel.org cgroup documentation.
The systemd.resource-control man page had references to /cgroups/ which
moved to /cgroup-v1/. (Closes: #819970)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie=d5e94d3fb

This patch has been cherry-picked from upstream. It was part of v230.
Small documentation update with no regression potential.


  * Don't start console-getty.service when /dev/console is missing.
Avoids repeated unsuccessful start attempts of agetty inside (docker)
containers. (Closes: #829537)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie=51d6e161e

This patch has been cherry-picked from upstream. It was part of v220, so
has seen quite a bit of testing in unstable/stretch. Very low regression
potential.

  * getty-static.service: Only start if we have a working VC subsystem.
Use ConditionPathExists=/dev/tty0, the same check as in getty@.service,
to determine whether we have a functional VC subsystem and we should
start any gettys. (Closes: #824779)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie=95dc10016

getty-static.service is a Debian specific addition, so this change is
not an upstream cherry-pick. This fix hasn't been uploaded to unstable
yet, but is atm only committed to master and pending. So strictly
speaking it violates the stable upload policy.
The one-line fix seemed obvious enough though to include it in the
upcoming jessie release and not defer for another cycle.
If you have any concerns regarding this change, I'm happy to back it out
again. It's a small fix which mostly helps LXC containers, which don't
have a real VC subsystem but start some pseudo-ttys on tty1-tty4. So the
check for /dev/tty2 was wrong. We had a discussion with systemd upstream
who recommends to test for /dev/tty0 as indicator for a working VC
subsystem.

 -- Michael Biebl   Sun, 24 Jul 2016 11:58:28 +0200


The complete debdiff is attached as well.

Thanks for considering,
Michael

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 974bbb0..6568877 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,30 @@
+systemd (215-17+deb8u5) stable; urgency=medium
+
+  * Use the right timeout for stop processes we fork. This ensures that
+services are properly killed after a given timeout. (Closes: #813702)
+  * Re-enable fsck -l. This 

Re: [Debian-med-packaging] migration exception for mhap

[Jonathan Wiltshire]

On 2016-07-23 23:14, Afif Elghraoui wrote:

على السبت 23 تـمـوز 2016 ‫06:56، كتب Jonathan Wiltshire:

On 2016-07-23 09:22, Afif Elghraoui wrote:

The latest upstream release of the mhap package adds a new dependency
on
libssw-java, which is not available for i386. The testing excuses 
page

for mhap currently says:

8 days old (needed 5 days)
mhap/i386 unsatisfiable Depends: libssw-java

May we have this package unblocked for migration?


No; you can't have a package in testing with unsatisfiable 
dependencies.

Either make libssw-java available on i386 or fix your dependencies.



mhap is arch:all. libssw-java contains Java bindings for its C library
and is not supported on i386. The dependencies are not broken. I hope
this is a clear enough explanation.


Yes, I know all that, but your dependencies are still broken. Your 
package is uninstallable on any architecture other than amd64.


For performance reasons britney only tests installability on amd64 and 
i386 (hence the message), otherwise the list would be much longer.


A package cannot migrate if it is not installable on the test 
architectures.



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

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

 i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits

Bug#828187: transition: rtmidi

[Jaromír Mikeš]

"

-- Původní zpráva --
Od: Emilio Pozuelo Monfort 
Komu: Jaromír Mikeš , 828...@bugs.debian.org
Datum: 28. 6. 2016 10:52:18
Předmět: Re: Bug#828187: transition: rtmidi

"Control: tags -1 confirmed

On 27/06/16 18:44, Jaromír Mikeš wrote:
> On 25/06/16 23:49, Jaromír Mikeš wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: transition
>>
>> Hi,
>> new upstream rtmidi bumps SONAME, so we need to transition.
>>
>> Direct reverse dependencies are:
>>
>> stk
>> giada
>> midisnoop
>> milkytracker
>>
>> Did you test build them?
> 
> Hi,
> 
> I just did test build of packages above.
> Location of header files changed from include to include/rtmidi so some 
easy patching will be needed.
> I just get some trouble to build midisnoop but not because of rtmidi 
package. 
> I am also maintainer of midisnoop and I don't see it as stopper for 
transition. 

Alright, go ahead. Please file bugs for the rdeps that need patches and let 
me
know which ones don't need any changes and can be rebuilt."



Ok bugs for r-deps filled ... unfortunately all of them need patches.



"



Hi,




all packages related to rtmidi transition are fixed and uploaded to 
unstable.

Can I now upload rtmidi 2.1.1 to unstable?




best regards




mira

Bug#832333: nmu: sikulix_1.1.0-1~exp3

[Andreas Beckmann]

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

nmu sikulix_1.1.0-1~exp3 . ANY . experimental . -m "Rebuild against 
libopencv-highgui2.4-deb0"

There was yet another opencv transition in sid ...

Andreas

Re: Bug#830267: dpkg: Segmentation fault when purging package in APT test case

[Francesco Poli]

On Thu, 7 Jul 2016 21:14:10 +0200 Guillem Jover wrote:

[...]
> On Thu, 2016-07-07 at 20:37:39 +0200, Julian Andres Klode wrote:
> > Package: dpkg
> > Version: 1.18.9
> > Severity: serious
> > 
> > dpkg fails to purge a package
[...]
> 
> Hmm, thanks for the report, I know where this is coming from, I'm
> fixing it and preparing an upload right away for later today.
[...]

Hello Guillem,
I see that this serious bug has been pending since July the 7th.
I thought dpkg/1.18.10 was going to be uploaded to unstable very soon
after having found the fix for this regression, but apparently
something went wrong.

In the meanwhile, dpkg/1.18.9 managed to migrate to testing [1], despite
introducing this RC bug: I wonder how that was even possible... do the
testing migration checks skip pending RC bugs?!? a pending bug is not a
fixed bug!!! I am Cc-ing the Release Team about this.

Dear Guillem, could you please clarify the status of this bug?

Dear Release Team, could you please explain what I failed to understand
about the testing migration rules [2]?

Please let me know, thanks for your time.



[1] https://tracker.debian.org/news/785311
[2] https://www.debian.org/devel/testing


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp7HXipql5_4.pgp
Description: PGP signature

Bug#830997: release.debian.org: Permission to consider dpkg-buildpackage -A bugs as RC

[Emilio Pozuelo Monfort]

On 23/07/16 19:20, Santiago Vila wrote:
> Kind Release Managers:
> 
> All the bugs reported by Lucas Nussbaum last week which have not been
> resolved yet are now either in "pending upload" state, or there is a
> patch available:
> 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=qa-indep;users=debian...@lists.debian.org
> 
> Because it was not expected that we would discover a lot more bugs of
> this type, I'd like this to be reconfirmed:
> 
> Still ok to consider this as a release goal?

Absolutely.

Thanks,
Emilio