Re: RFS to solve bug#999962 (silversearcher-ag: depends on obsolete pcre3 library)

2023-09-10 Thread Manphiz
Nicholas D Steeves writes: > Nicholas D Steeves writes: > > >> As for facts: It looks like the Debian maintainer of this package didn't >> document copyright and license for the m4 stuff (your sponsor might >> require this), and your patch is not work by Geoff Greer, so you'll >> probably need t

closql-el is marked for autoremoval from testing

2023-09-10 Thread Debian testing autoremoval watch
closql-el 1.2.1-3 is marked for autoremoval from testing on 2023-10-16 It (build-)depends on packages with these RC bugs: 1051090: emacsql: FTBFS: 5 unexpected results https://bugs.debian.org/1051090 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/m

emacsql is marked for autoremoval from testing

2023-09-10 Thread Debian testing autoremoval watch
emacsql 3.1.1+ds-1 is marked for autoremoval from testing on 2023-10-16 It is affected by these RC bugs: 1051090: emacsql: FTBFS: 5 unexpected results https://bugs.debian.org/1051090 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autore

emacsql-sqlite3 is marked for autoremoval from testing

2023-09-10 Thread Debian testing autoremoval watch
emacsql-sqlite3 1.0.2+git20220304.1.2113618-1 is marked for autoremoval from testing on 2023-10-16 It (build-)depends on packages with these RC bugs: 1051090: emacsql: FTBFS: 5 unexpected results https://bugs.debian.org/1051090 This mail is generated by: https://salsa.debian.org/release-team/

ol-notmuch is marked for autoremoval from testing

2023-09-10 Thread Debian testing autoremoval watch
ol-notmuch 2.0.0-2 is marked for autoremoval from testing on 2023-10-16 It (build-)depends on packages with these RC bugs: 105: notmuch: FTBFS: 6 tests failed. https://bugs.debian.org/105 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/maile

magit-forge-el is marked for autoremoval from testing

2023-09-10 Thread Debian testing autoremoval watch
magit-forge-el 0.3.2-1 is marked for autoremoval from testing on 2023-10-16 It (build-)depends on packages with these RC bugs: 1051090: emacsql: FTBFS: 5 unexpected results https://bugs.debian.org/1051090 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/mas

Bug#1051247: muse-el: Choose living upstream for muse-el and merge updates

2023-09-10 Thread Manphiz
Nicholas D Steeves writes: > Hi manphiz, > > Manphiz writes: > >> Xiyue Deng writes: >> >> Hi sten, >> >> When trying to pick a new upstream to rebase, I found that pulling >> either upstream repo will result in an incompatible git history versus >> the current debian/master branch on salsa. >

Bug#1051247: muse-el: Choose living upstream for muse-el and merge updates

2023-09-10 Thread Nicholas D Steeves
Hi manphiz, Manphiz writes: > Xiyue Deng writes: > > Hi sten, > > When trying to pick a new upstream to rebase, I found that pulling > either upstream repo will result in an incompatible git history versus > the current debian/master branch on salsa. This is expected, but please merge from ups

circe_2.12-1_source.changes ACCEPTED into unstable

2023-09-10 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Sep 2023 11:49:31 -0300 Source: circe Architecture: source Version: 2.12-1 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen Team Changed-By: David Br

Processing of circe_2.12-1_source.changes

2023-09-10 Thread Debian FTP Masters
circe_2.12-1_source.changes uploaded successfully to localhost along with the files: circe_2.12-1.dsc circe_2.12.orig.tar.gz circe_2.12-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1051247: muse-el: Choose living upstream for muse-el and merge updates

2023-09-10 Thread Manphiz
David Bremner writes: > Manphiz writes: > >> >> Hi sten, >> >> When trying to pick a new upstream to rebase, I found that pulling >> either upstream repo will result in an incompatible git history versus >> the current debian/master branch on salsa. I wonder how I should handle >> this? Is it